Skip to main content
Glama

get_vendor_benchmark

Read-only

Use when a CFO or procurement lead needs org-specific vendor pricing vs market before renewal or negotiation. Returns market_low, market_median, market_high, position_label, negotiation tactics, estimated_savings_monthly from benchmark_cache when fresh, or guidance to load intelligence in Stratalize. Example: Salesforce median ~$8,400/mo — recoverable gap when spend exceeds monthly_high. Source: benchmark_cache + Stratalize composites. $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_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYesName of the vendor to benchmark (e.g. HubSpot, QuickBooks, Salesforce)
mcp_client_sourceNoOptional client identifier for analytics (e.g. host app or integration name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses the data sources (benchmark_cache + Stratalize composites), the stale-cache fallback behavior (returns guidance to load intelligence in Stratalize), and the cost of $0.10 USDC per call. That paid-per-call detail is exactly the kind of trait an agent must know before invoking.

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?

Front-loaded with the usage trigger, then return fields, fallback, example, sources, and price — each sentence carries information. The returned-field sentence runs long and the fallback clause is tangled mid-sentence, costing some readability.

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

Completeness5/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 compensates by enumerating the return fields (market_low/median/high, position_label, negotiation tactics, estimated_savings_monthly) and a concrete example. Source, fallback, and price complete the picture an agent needs before calling.

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 both parameters are already documented in the schema. The description adds context about what 'org-specific' implies but gives no format or syntax detail for vendor_name beyond what the schema provides. Baseline 3 applies when the schema carries the load.

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 concrete verb and resource ('org-specific vendor pricing vs market') plus the decision context (renewal or negotiation). An agent can tell this is a vendor pricing benchmark, but it never distinguishes itself from closely related siblings such as get_vendor_market_rate or get_vendor_negotiation_intelligence.

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?

'Use when a CFO or procurement lead needs org-specific vendor pricing vs market before renewal or negotiation' gives a clear triggering situation and persona. It stops short of exclusions or naming an alternative when the sibling market-rate or negotiation tools would be more appropriate.

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