Model Context Protocol tools for Vendr software pricing insights
Three tools with documented input/output schemas and descriptions. Tool naming follows verb_noun pattern (get*, search*). Input schemas are well-structured with proper types and nested objects. However, parameter descriptions lack actionable guidance on constraints, ranges, and error recovery. Output schemas are not explicitly documented in the source code excerpts provided. Two tools (searchCompaniesAndProducts, getNegotiationInsights) have generic or vague descriptions that don't clearly explain when to use them relative to other tools. Error handling exists but lacks recovery guidance. Tool composition is reasonable (tools chain together for pricing workflow) but descriptions could better explain the sequential/parallel usage pattern mentioned in getNegotiationInsights.
Get a customized price estimate based on scope details including product terms, pricing dimensions, and scope terms. Optionally present up to 3 similar real purchases following the price benchmark.
Vendr MCP Tools provide software pricing insights by adding Vendr's proprietary catalog data to publicly available pricing information. When asked about software pricing, use these tools together (sequentially or in parallel) to guide users through Vendr's hierarchical catalog (categories → sub-categories → companies → product families → products → pricing dimensions) and help them to generate customized software price estimates.
Search for companies and products in the Vendr catalog. Helps guide users through the hierarchical catalog structure (categories → companies → product families → products).
searchCompaniesAndProducts has no visible input schema definition in provided source code. Only tool name exists; parameter structure unknown.
getNegotiationInsights has minimal input schema (only companyId shown). Output schema not documented. Unclear what fields the response contains or whether pagination is supported.
Parameter descriptions in getCustomPriceEstimate lack actionable constraints. E.g., 'listPrice', 'discount', and 'finalPrice' numeric fields have no min/max bounds. 'termLength' accepts any integer, should specify realistic range (e.g., 1-60 months). No guidance on field relationships (e.g., finalPrice = listPrice - discount).
searchCompaniesAndProducts description is generic and does not explain when to call it vs. getNegotiationInsights. LLM cannot determine which search tool to use based on the provided descriptions.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 58 | 2025-06-18+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
getNegotiationInsights description conflates tool documentation with task description. It describes the overall workflow ('use these tools together') rather than what this specific tool does. Not clear whether it returns insights, recommendations, or negotiation strategies.
No output schemas documented in code. LLMs cannot plan downstream tool calls or extract needed fields without knowing response structure. Per pattern:tool, output schemas must be documented.
No visible error handling guidance in tool descriptions. If an API call fails (invalid UUID, missing companyId), the LLM receives no recovery hint. Descriptions should state: 'If company not found, call searchCompaniesAndProducts first.'
getCustomPriceEstimate accepts optional fields (autoRenew, startDate, endDate, listPrice, discount, finalPrice) at scope and product levels. No documentation of which combinations are valid or what happens if only finalPrice is provided without listPrice/discount breakdown.