Skip to main content
Glama

Stratalize Intelligence

Get Vendor Market Rate

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses several behaviors an agent could not infer: a composite-median fallback when no vendor-specific row exists, the exact returned fields including a freshness stamp (data_as_of), the data source, and a per-call cost of $0.10 USDC. It does not say what happens for an unknown vendor or whether the fallback is flagged as non-vendor-specific in the response.

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

Conciseness4/5

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

The description is front-loaded with the triggering condition and packs high-value facts (returned fields, fallback, source, price) into a few sentences with no filler. The field enumeration is dense but justified because no output schema exists.

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

Completeness4/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 and adds cost, source, and fallback semantics for a paid external lookup. Remaining gaps are edge-case behavior: unknown vendors, how industry/company_size affect the medians, and whether fallback results are visibly distinguished.

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 coverage is 100%, so vendor_name, industry, and company_size are already documented in the schema, and the description adds no syntax, matching rules, or fallback-matching behavior for them. It only implicitly relates the lookup to vendor-specific rows, which is baseline-level value when the schema does the heavy lifting.

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?

The description states a specific verb and resource ('vendor market rate' lookups returning monthly/annual price medians and ranges) and frames the business question it answers (are we overpaying for a software vendor). It stops short of distinguishing itself from close siblings such as get_vendor_benchmark or get_healthcare_vendor_market_rate, and it mixes a healthcare-benchmark source with a Salesforce CRM example, which blurs the scope slightly.

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?

It gives a clear triggering context ('when a CFO or procurement team needs to know if they are overpaying') and an interpretation rule (organizations above monthly_high are overpaying). There is no when-not guidance and no explicit routing to alternative tools for general vs. healthcare vendor benchmarking.

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