Skip to main content
Glama

get_category_spend_benchmark

Read-only

Use when benchmarking total spend in a software category against same-size peers. Returns median monthly spend, p25/p75 band, and sample size for any software category by company size. Example: Mid-market CRM spend median ~$3,500/mo, p75 of $4,900 — organizations above p75 have a negotiation mandate supported by market data. Source: Stratalize enterprise spend composite. $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": {
      "category": "<category>"
    },
    "name": "get_category_spend_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesSoftware or service category
industryNo
company_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, and open-world, so the safety profile is covered; the description adds useful value with the returned statistics (median, p25/p75, sample size), the data source (Stratalize composite), and a per-call price of $0.10 USDC. That pricing detail is genuinely beyond the annotations and helps an agent weigh cost. The unit and currency of the returned spend figures are not specified, which the negotiation-mandate framing leaves ambiguous for an open-world benchmark.

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 trigger condition is front-loaded and the return shape and pricing follow in a compact sequence, so an agent can stop reading after the first two sentences. The example sentence drifts into sales framing about a 'negotiation mandate,' which is longer than needed for tool selection and pairs loosely with the numeric example it illustrates.

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 rightly enumerates the returned fields, which is the most important gap to fill. It still omits units/currency for the spend figures, valid values for company_size, and the meaning of the industry parameter, so an agent can construct a call but not predict how optional parameters change 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 coverage is 33%, with only 'category' documented, so the description does important work in confirming that results are segmented by company size and that any software category is valid. However, the 'industry' parameter is never mentioned anywhere, and 'company_size' has no guidance on accepted values despite having no enum in the schema. The description partially compensates for the coverage gap but leaves a real undefined parameter.

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 action and metric (benchmarking total spend in a software category) and scopes it to same-size peers, which is enough to distinguish it from a generic spend query. It does not explicitly contrast itself with the closest siblings (get_industry_spend_benchmark, get_spend_by_company_size), so the differentiation is implicit rather than stated.

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 opens with an explicit trigger, 'Use when benchmarking total spend in a software category against same-size peers,' which tells the agent exactly the situation that selects this tool. It gives no when-not conditions and does not name a preferred alternative for industry-level or overall-spend questions, leaving the routing to inference.

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