GSA CALC+

keyword_search

Read-only

Search GSA CALC+ ceiling rates by keyword.

Performs wildcard matching across labor_category, vendor_name, and
idv_piid fields. This is the primary search tool for finding rates.

Returns matching rate records plus aggregation statistics (wage_stats,
percentiles, education breakdown, business size) covering the FULL
result set even when individual hits are capped at 10,000.

Important notes:
- These are NTE (not-to-exceed) ceiling rates, not prices paid
- Rates are fully burdened hourly rates from GSA MAS contracts
- Data refreshes nightly from vendor price proposal tables
- Use P50 from percentiles for median (more accurate than median_price)

Filter parameters:
- education_level: AA, BA, HS, MA, PHD, TEC (pipe-delimited for OR: 'BA|MA')
- experience_min/max: years of experience range
- price_min/max: hourly rate range in USD
- business_size: 'S' (small) or 'O' (other/large)
- security_clearance: 'yes' or 'no'
- sin: Special Item Number (e.g., '54151S' for IT Professional Services)
- worksite: NOT supported (the v3 API silently ignores it; passing a
  value raises so callers are not handed unfiltered data)

ordering: current_price, labor_category, vendor_name, education_level,
min_years_experience, next_year_price, idv_piid, business_size.
sort: 'asc' or 'desc'.

exclude: pipe-delimited hit _id values to exclude from results and stats.

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": {
      "keyword": "<keyword>"
    },
    "name": "keyword_search"
  }
}

Input Schema

Name	Required	Default
`sin`	No
`page`	No
`sort`	No	asc
`exclude`	No
`keyword`	Yes
`ordering`	No	current_price
`worksite`	No
`page_size`	No
`price_max`	No
`price_min`	No
`business_size`	No
`experience_max`	No
`experience_min`	No
`education_level`	No
`security_clearance`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: aggregation stats cover the full result set even when hits are capped at 10,000, rates are NTE ceiling rates rather than prices paid, data refreshes nightly, and worksite is unsupported and raises instead of silently returning unfiltered data.

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?

The description is front-loaded with the core purpose and then uses compact sections for return behavior, domain caveats, filters, ordering, and exclusion. It is long but appropriately dense for a 15-parameter search tool, and every section adds actionable context.

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?

Given the complex parameter surface, the read-only annotations, and the presence of an output schema, the description provides enough domain and behavioral context for an agent to call the tool correctly. The main omissions are standard pagination details, which are less critical here and do not undermine correct use.

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 description coverage is 0%, so the description must carry parameter meaning, and it documents most important filters, ordering fields, sorting, exclusion, and the worksite pitfall. It still leaves page, page_size, and keyword syntax/details largely to the schema, which is a meaningful but not severe gap for 15 parameters.

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 states a specific verb and resource: search GSA CALC+ ceiling rates by keyword. It also specifies wildcard matching across labor_category, vendor_name, and idv_piid, which makes its role distinct from exact_search and filtered_browse even without naming them.

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 clearly positions itself as the primary search tool for finding rates and gives substantial filter guidance. However, it does not explicitly say when to use exact_search or filtered_browse instead, so the routing guidance is strong but not complete.

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

All GSA CALC+ tools Inspect

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.