Skip to main content
Glama

get_industry_spend_benchmark

Read-only

Use when validating total IT spend against industry peers or building a software budget baseline for a CFO board presentation. Returns median monthly total software stack spend, category breakdown, and productivity tool medians by industry. Example: Mid-market healthcare org — median total SaaS spend $18,500/mo, EHR and clinical tools 41% of stack, productivity suite $2,800/mo — organizations above $26,000/mo are consolidation candidates. Source: Stratalize industry 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": {
      "industry": "<industry>"
    },
    "name": "get_industry_spend_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYes
company_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world behavior, so the description's value-add is provenance and cost: 'Source: Stratalize industry composite' and '$0.10 USDC per call' tell the agent where the data comes from and that invocation has a real per-call charge. It also previews the concrete shape of the response through a worked healthcare example. Remaining gaps are minor, such as whether results are cached or how stale the composite is.

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?

It is front-loaded with the use case, then the return set, then a concrete example, then provenance and price — a logical order with no filler sentences. The example is slightly verbose and the 'consolidation candidates' framing is decorative rather than actionable, but nothing is redundant.

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 does a good job explaining what comes back and even quantifies an example response. However, for a two-parameter tool with zero schema documentation, it leaves an agent unable to construct a valid call without guessing at industry strings and size buckets, and never clarifies optionality of company_size.

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

Parameters2/5

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

Schema description coverage is 0%, so both 'industry' and 'company_size' carry no documented meaning in the structured fields. The description only implicitly illustrates them via the 'Mid-market healthcare org' example, and never states accepted industry values, valid company-size buckets, or that company_size is optional. That is insufficient compensation for a complete schema documentation gap.

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 resource and return set: median monthly total software stack spend, category breakdown, and productivity tool medians by industry. An agent can tell this is a software-spend benchmarking lookup rather than a generic industry profile or a single-category lookup. It stops short of explicitly distinguishing itself from near-named siblings such as get_industry_spend_profile or get_category_spend_benchmark.

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 validating total IT spend against industry peers or building a software budget baseline for a CFO board presentation" gives concrete triggering contexts, including a named audience and deliverable. No when-not guidance or named alternative is offered, so the agent cannot tell from the description which sibling to pick for overlapping questions.

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