Skip to main content
Glama

Gsa Vendor Rates

gsa_vendor_rates
Read-onlyIdempotent

Every GSA schedule labor rate published by one contractor, what this specific company charges the government per hour, across its labor categories, with contract numbers and SINs. Use for "what rates does Booz Allen have on its GSA schedule" or to compare one vendor against the market median. Example: gsa_vendor_rates({ vendor: "DIGNITAS TECHNOLOGIES" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rates to return, 1-200 (default 25).
vendorYesCompany name or a distinctive fragment of it, e.g. "DIGNITAS" or "Booz Allen". Vendor names are recorded in full legal form on the contract.
sort_byNoSort field (default current_price).
max_rateNoOnly rates at or below this hourly price, USD.
min_rateNoOnly rates at or above this hourly price, USD.
sort_dirNoSort direction (default asc).
worksiteNoWhere the work is performed: "contractor" (vendor site) or "customer" (government site).
educationNoMinimum education: HS, AA, BA or MA. Plain spellings work too ("bachelors", "high school"). Combine with | for several, e.g. "BA|MA".
business_sizeNo"S" for small business or "O" for other than small. "small" and "large" also work.
max_experienceNoMaximum years of experience required, inclusive.
min_experienceNoMinimum years of experience required, inclusive. Means "this many OR MORE", mapped to the upstream range filter, because the upstream field of the same name is an exact match.
security_clearanceNo"yes" to only rates requiring a clearance, "no" to exclude them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / min_experience / description
      Previous value: -"Minimum years of experience required, inclusive. Means \"this many OR MORE\" — mapped to the upstream range filter, because the upstream field of the same name is an exact match."New value: +"Minimum years of experience required, inclusive. Means \"this many OR MORE\", mapped to the upstream range filter, because the upstream field of the same name is an exact match."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description's real contribution is disclosing the shape of the response (hourly rates across labor categories, with contract numbers and SINs), which matters because there is no output schema. It says nothing about rate limits, behavior on ambiguous or non-matching vendor names, or result volume beyond what the limit parameter implies.

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?

The core scope is front-loaded in the first clause, followed by usage framing and one example call. There is mild internal redundancy between "every GSA schedule labor rate published by one contractor" and "what this specific company charges the government per hour," but nothing that wastes a sentence.

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 12-parameter read tool with full schema coverage and complete annotations, the description covers purpose, use cases, and return content. The remaining gaps are edge-case behavior (multiple vendor matches, empty results) that an agent would benefit from but that are not essential to invoking it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 12 parameters including defaults, enums, and the min_experience mapping quirk. The description only reinforces the vendor-as-name-fragment idea through its example call and adds no syntax or filtering guidance the schema lacks. Baseline 3 applies.

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 a specific resource and scope: every GSA schedule labor rate published by ONE contractor, broken out by labor category and carrying contract numbers and SINs. The single-vendor scoping implicitly contrasts with a market-wide rates tool, but no sibling is named, so differentiation relies on inference.

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 gives two concrete use cases ("what rates does Booz Allen have on its GSA schedule" and comparing one vendor against the market median) plus a worked call example, which is clear placement guidance. It stops short of explicit when-not-to-use conditions or naming the alternative tool for the market-median comparison.

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.