Skip to main content
Glama

get_spend_by_company_size

Read-only

Use when benchmarking software category spend against same-size organizations before a purchase or renewal. Returns SMB, mid-market, and enterprise median monthly spend for any software category. Example: CRM median spend — SMB $1,200/mo, mid-market $8,400/mo, enterprise $42,000/mo — 35x spread confirms size-appropriate benchmarking before any negotiation. Source: Stratalize size-segmented 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": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_spend_by_company_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered; the description adds genuinely new behavioral facts: the exact return shape (three size bands of median monthly spend), the data source (Stratalize size-segmented composite), and a per-call cost of $0.10 USDC, which matters for agent budget decisions. It does not state coverage limits or what happens for a category with no data, but the added cost and source disclosure is well beyond the annotations.

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 shape, then a concrete numeric example, then source and price — a sensible order with no filler paragraphs. The clause "35x spread confirms size-appropriate benchmarking before any negotiation" restates the opening sentence in promotional language and could be cut.

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 correctly spells out what comes back (median monthly spend by size band) and even quantifies it, which is the main completeness win. However, for a one-parameter tool with zero schema documentation it leaves the key input contract — what exactly goes in vendor_name — unresolved, which is a material gap for correct invocation.

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% for the single required parameter, vendor_name, so the description carries the full burden — and it never mentions the parameter at all. Worse, it frames the input as "any software category" and uses "CRM" as the example, which suggests passing a category name into a field called vendor_name; that ambiguity could cause wrong invocations.

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 specific verb and resource — benchmarking software category spend against same-size organizations — and returns a named breakdown (SMB, mid-market, enterprise median monthly spend). The size-segmentation angle is what separates it from category- or industry-level benchmark siblings, so an agent can pick it 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?

"Use when benchmarking ... before a purchase or renewal" gives a concrete trigger scenario rather than a generic one. It does not name an explicit alternative or exclusion (e.g., when to prefer an industry benchmark instead), so routing between the many benchmark siblings still requires 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