Skip to main content
Glama
Sign In

SpendQuery

by com.spendquery
OverviewDiscussionsAdmin

Look up typical award sizes and labor rates

award_prices
Read-onlyIdempotent

For pricing a bid: what contracts in an industry (and state) are typically worth over the last three complete fiscal years (percentiles of award values by kind: definitive contracts, purchase orders, orders under vehicles; by set-aside and competition), and GSA schedule ceiling hourly rates (CALC+) for a labor category. Never a suggested price.

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": "award_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
naicsNoA NAICS code, 2-6 digits, e.g. "561720".
stateNoA state code to narrow award sizes, e.g. "VA".
labor_categoryNoA labor category for GSA ceiling rates, e.g. "senior software engineer".
small_business_ratesNoLabor rates of small businesses only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description is not obliged to restate safety. It adds real context beyond them: the three-complete-fiscal-year window, that values are percentiles rather than raw listings, the CALC+ source for rates, and the caveat that this is not a suggested price.

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 a single dense sentence with the pricing purpose front-loaded and the crucial caveat last; every clause carries information. The nested parentheticals make it harder to scan than it needs to be, which keeps it out of the top band.

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?

For a zero-required-parameter, read-only lookup with no output schema, the description covers the data windows, the dimensions returned, and the interpretation limit. It leaves the shape of the return (percentile labels, units, how the two result families are combined) implicit, which is the main remaining gap.

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 goes further by mapping inputs to outputs: industry and state drive award-size percentiles, while labor category drives GSA ceiling rates. The set-aside dimension implicitly explains the small_business_rates flag. Minor gap: it never states that all parameters are optional or what happens when they are omitted.

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 resource and verb: percentile award values by industry/state over the last three complete fiscal years, plus GSA schedule ceiling hourly rates (CALC+) for a labor category. It also enumerates the breakdowns (kind, set-aside, competition), so an agent can tell this apart from any sibling lookup tool 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?

"For pricing a bid" gives a clear situational trigger and "Never a suggested price" sets a boundary on interpretation. It does not name alternative siblings or state when-not-to-use (e.g., when the agent instead wants a specific award record), so it falls short of the explicit routing a 5 requires.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SpendQuery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources