Skip to main content
Glama

get_vendor_market_rate

Read-only

Use when a CFO or procurement team needs to know if they are overpaying for any software vendor. Returns monthly_median, monthly_low, monthly_high, annual_median, pricing_model, source, and data_as_of from healthcare vendor benchmark lookups with Stratalize composite medians as fallback when no vendor-specific row exists. Example: Salesforce CRM median ~$8,400/mo — organizations above the monthly_high range are overpaying by a recoverable margin. Source: healthcare_vendor_benchmarks with Stratalize composite medians. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_vendor_market_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoOptional industry filter
vendor_nameYesVendor name to look up
company_sizeNoOptional company size segment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds real value beyond them: a fallback behavior (Stratalize composite medians when no vendor-specific row exists), a data source, a staleness field (data_as_of), a cost of $0.10 USDC per call, and how to interpret results (>monthly_high means overpaying by a recoverable margin). Missing only what happens with the industry/company_size filters when no match exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage trigger is correctly front-loaded, but the body is a run-on sentence listing seven fields, and the data-source statement ('healthcare_vendor_benchmarks with Stratalize composite medians') is repeated twice, wasting space in an already dense definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates return fields, sources, and pricing, which covers most of what an agent needs. However, it never resolves whether this tool is healthcare-only or general-purpose software benchmarking, which is the decisive fact for selecting it correctly among the vendor/market-rate siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (vendor_name, industry, company_size) are already documented by the schema; baseline is 3. The description adds no guidance on filter semantics, such as what granularity vendor_name accepts or how industry/company_size narrow or fall back to composite medians.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (look up) and resource (software vendor market rate / benchmark pricing) plus the concrete return fields (monthly_median, monthly_low, monthly_high, annual_median, pricing_model, source, data_as_of). The purpose is unmistakable, but the scope is muddied by describing the data as 'healthcare vendor benchmark lookups' while the tool name implies general software vendors, leaving overlap with a healthcare-specific sibling unresolved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition and persona: 'Use when a CFO or procurement team needs to know if they are overpaying for any software vendor,' backed by a concrete overpaying-detection example. It does not state when NOT to use it or name an alternative for the healthcare-specific or contract-intelligence adjacent cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources