Skip to main content
Glama

Stratalize Intelligence

Get Vendor Benchmark

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

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety bar is low, but the description still adds real value: a data source (benchmark_cache + Stratalize composites), a freshness fallback (returns guidance to load intelligence when cache is stale), and a per-call cost of $0.10 USDC. It does not cover identity-matching behavior (what happens when the vendor is not in cache) or result latency/billing failure modes, so it is good rather than exemplary.

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 outputs, then fallback, example, source, and price — a sensible ordering with little waste. The single dense block with em-dash and example makes it slightly harder to scan than a partitioned structure would be.

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?

For a read-only two-parameter tool with no output schema, the description supplies what the schema cannot: the return field list, the cache-vs-fallback behavior, an illustrative example, the data provenance, and the price. An agent has everything needed to decide to call it and to interpret the result.

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% and both parameters are already documented with examples, so the baseline of 3 applies. The description adds no semantics about vendor_name matching (fuzzy vs exact, aliases) or what mcp_client_source does beyond the schema text.

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 names a specific verb+resource (benchmark a vendor's org-specific pricing against market) and enumerates concrete return fields (market_low/median/high, position_label, estimated_savings_monthly). It falls short of a 5 because several sibling tools (get_vendor_market_rate, get_vendor_negotiation_intelligence, get_vendor_contract_intelligence) sound adjacent and the description never distinguishes itself from them.

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 trigger, audience, and timing. There is no when-not guidance and no named alternative for adjacent needs (e.g. contract terms or negotiation playbooks), which keeps it below 5.

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