Skip to main content
Glama

get_industry_spend_profile

Read-only

Use when sizing a technology budget for a specific industry and headcount, or identifying category spend outliers. Returns spend bands, category ranges, and outlier flags scaled to employee count. Example: 500-person healthcare org — total SaaS stack median $1.2M/yr, EHR 34% of spend, clinical productivity tools 18% — organizations above $1.8M are consolidation candidates. Source: Stratalize workforce-scaled composite. $0.02 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>",
      "employee_count": "<employee_count>"
    },
    "name": "get_industry_spend_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYesIndustry vertical
employee_countYesEmployee headcount for banding

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds genuinely new behavior: a per-call price of $0.02 USDC and the provenance of the data (Stratalize workforce-scaled composite). The example output also reveals interpretive thresholds (organizations above $1.8M are consolidation candidates), which is useful for downstream reasoning, though latency and coverage limits of the composite are unstated.

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

Conciseness5/5

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

Front-loaded with a 'Use when' trigger, then return contents, then a worked example, then source and price. No sentence is filler; the example is long but carries real interpretive value.

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 only two required parameters, no output schema, and light annotations, the description covers the full burden: what it returns, how parameters affect output, where the data comes from, and what it costs. An agent can decide to call it and interpret the result without further information.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by showing how employee_count drives scaling and how industry shapes category mix (a 500-person healthcare org with EHR at 34%). The concrete example makes the effect of both parameters tangible rather than merely restating their types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource and scope: technology-budget sizing by industry and headcount, returning spend bands, category ranges, and outlier flags. That output signature (workforce-scaled bands plus outlier flags) is specific enough to separate it from generic benchmark tools in the sibling list without opening the schema.

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?

The opening clause gives two explicit triggering conditions: sizing a technology budget for a given industry/headcount, and identifying category spend outliers. It does not state when-not to use it or name a preferred alternative, so it falls short of a 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