Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

calc_search_rates

Read-onlyIdempotent

Search awarded hourly rates on GSA MAS contracts to find ceiling rates for market research, IGCEs, and competitive pricing.

Instructions

Search GSA CALC+ ceiling rates for federal labor categories. Find awarded hourly rates on GSA MAS professional services contracts. Search by keyword (wildcard across labor category, vendor, contract), exact field match, or browse with filters. Useful for market research, IGCEs, and competitive pricing. Data refreshed daily.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinNoGSA SIN (Special Item Number) - e.g. '541330ENG', '541620'
pageNoPage number (default 1)
sortNoSort direction (default: asc)
searchNoExact field match as 'field:value' - e.g. 'labor_category:Engineer II', 'vendor_name:Deloitte', 'idv_piid:GS10F0303V'
keywordNoWildcard keyword search across labor category, vendor name, and contract number (2 char min) - e.g. 'software engineer', 'Booz', 'GS10F'
categoryNoService category - e.g. 'Professional Services', 'Facilities'
orderingNoSort field: 'labor_category', 'current_price', 'education_level', 'keywords', 'certifications', 'min_years_experience', 'vendor_name', 'schedule'. Default: current_price
worksiteNoWorksite: 'Contractor', 'Customer', 'Both'
page_sizeNoResults per page (default 20)
price_rangeNoHourly rate range as 'min,max' dollars - e.g. '50,150'
subcategoryNoService subcategory - e.g. 'IT Services', 'Engineering'
business_sizeNoBusiness size: 'S' (Small Business), 'O' (Other than Small Business)
education_levelNoEducation filter: 'HS', 'AA', 'BA', 'MA', 'PHD'. Use pipe for multiple: 'BA|MA'
experience_rangeNoExperience range as 'min,max' years - e.g. '3,10' or '5,20'
security_clearanceNoSecurity clearance required: 'yes' or 'no'
min_years_experienceNoExact minimum years - e.g. '5'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.9.14
    • addedInput schema / properties / page_size / default
      Added value: +20
  2. Changed1 schema field changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2026.3.9

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds that data is refreshed daily and explains the three search modes (keyword wildcard, exact field match, filters), which are behavioral details beyond the annotations. No contradiction.

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?

Five concise sentences, each with a distinct purpose: purpose, resource, search modes, use cases, data freshness. No fluff and front-loaded with the core action.

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?

For a 16-parameter search tool with no output schema, the description provides a complete mental model: what data is searched, how to search it (three modes), why it's useful, and data freshness. The schema handles parameter details, so the description only adds necessary context.

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 covers 100% of parameters with descriptions. The description adds high-level semantics: keyword is wildcard across labor category, vendor, contract; search is exact field match; other params serve as filters. This goes beyond the schema's individual field descriptions.

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?

States a specific verb ('Search') and resource ('GSA CALC+ ceiling rates for federal labor categories'), and clarifies it finds awarded hourly rates on GSA MAS professional services contracts. This distinguishes it from sibling calc_contract_rates by focusing on ceiling rates specifically.

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?

Explicitly states useful for market research, IGCEs, and competitive pricing, giving clear context for when to use. Does not name alternatives or exclusions, so not a full 5.

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

Deploy Server

Other Tools