Skip to main content
Glama

Published range for a company

instant_range
Read-onlyIdempotent

The span of published per-company figures across the buyer programs a company of this size and age clears, with every source named and quoted. Give headcount and years if you know them; a company that has not stated one is not screened on it. A program is dropped only when the company certainly cannot meet its own stated floor. A /data band is screened the way /data screens it, at the top of the band, so a program is dropped only when the whole band is below its floor; the answer echoes the band, the figure it was screened as, and the programs that depend on where in the band the company sits. Returns has_range: false, with a reason, when fewer than two programs qualify — one program's advertisement is not a range, and no figure is estimated to fill the gap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instant_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoYears of records the company holds. Omit if unknown.
headcountNoFull-time employees. Omit if unknown.
years_bandNoA /data years band instead of an exact figure: under_3, 3_5, 6_10, 11_plus.
headcount_bandNoA /data headcount band instead of an exact figure: 1_29, 30_99, 100_249, 250_plus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the actual screening rule (a program is dropped only when the company certainly cannot meet its own stated floor), how band inputs are screened, and the failure mode: has_range: false with a reason when fewer than two programs qualify, and an explicit no-estimation policy. That is exactly the kind of edge-case and fallback behavior an agent needs before calling.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence and every later sentence carries information, but the prose is dense and convoluted ('A /data band is screened the way /data screens it, at the top of the band'), forcing re-reads. It could convey the same rules in noticeably fewer, cleaner sentences.

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 must carry return-value meaning, and it does partially: has_range, the reason field, the echoed band/figure, and the qualifying programs. It stops short of describing the overall response shape (how sources and figures are structured), which is the main remaining gap for a computation-heavy tool.

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, but the description adds real meaning: omitted figures are not screened, and band inputs cause the answer to echo the band plus the figure it was screened as. This explains the semantic difference between the exact and band parameters that the schema only lists.

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 the resource precisely: the span of published per-company figures across buyer programs a company of a given size and age clears, with sources named and quoted. It is clearly a range-lookup tool rather than a list/get tool, though the jargon ('/data band', 'programs') and the absence of any named sibling keep it from being a clean 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: supply headcount/years (or bands) to get qualifying programs. There is useful guidance on omitted inputs ('a company that has not stated one is not screened on it'), but no explicit when-to-use framing and no routing to or away from alternatives such as search_data_buyers or read_data_offer.

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