Skip to main content
Glama

Stratalize Intelligence

Get Industry Spend Profile

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

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world). The description adds material context they cannot: the data provenance ('Stratalize workforce-scaled composite') and a per-call price of $0.02 USDC, which is critical for an agent deciding whether to call it. It does not mention auth or rate limits.

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?

Usage conditions are front-loaded, and the example is long but earns its space because there is no output schema to convey return shape. The pricing note is tacked on the end but is short and high-value.

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

Completeness4/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 carries the burden and largely meets it by describing the returned artifacts and giving a concrete numeric example for a 500-person healthcare org. Minor gaps remain around units/currency and the exact form of 'outlier flags' and 'consolidation candidate' thresholds.

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 100%, including an enum for industry, so the two parameters are already fully documented. The worked example implies how employee_count drives banding but adds no syntax or handling detail beyond the schema. Baseline 3 applies.

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 (industry spend profile) and enumerates the outputs: spend bands, category ranges, and outlier flags scaled to employee count. It is clearly not a benchmark-average tool like the sibling get_industry_spend_benchmark, though it never explicitly contrasts itself with that sibling.

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 gives explicit triggering conditions — 'sizing a technology budget for a specific industry and headcount' or 'identifying category spend outliers' — which is more than most definitions offer. It stops short of naming when NOT to use it or pointing to an alternative tool for benchmarking.

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