Skip to main content
Glama

Gsa Labor Rates

gsa_labor_rates
Read-onlyIdempotent

GSA schedule hourly labor rates for a job title, the ceiling rate vendors may charge the government under a GSA MAS contract. Use this to benchmark what a labor category costs: "typical GSA hourly rate for a project manager", "what do senior software engineers bill under MAS", "GSA schedule rate for a data scientist with 10 years experience". Returns individual rates with vendor name, contract number, SIN, education and experience requirements, plus a price summary (min, p25, median, p75, max) computed across EVERY matching rate, not just the ones returned. Filter by experience, education, worksite, business size, security clearance and price band. Example: gsa_labor_rates({ labor_category: "software engineer", min_experience: 5 })

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": {
      "labor_category": "software engineer",
      "min_experience": 5
    },
    "name": "gsa_labor_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many individual rates to return, 1-200 (default 25). The summary always covers every matching rate regardless of this.
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.
labor_categoryYesJob title to benchmark, e.g. "software engineer", "project manager". Partial match against contract labor categories, which are free text, prefer a short phrase over a long one.
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. Changed2 schema fields changed
    • changedInput schema / properties / labor_category / description
      Previous value: -"Job title to benchmark, e.g. \"software engineer\", \"project manager\". Partial match against contract labor categories, which are free text — prefer a short phrase over a long one."New value: +"Job title to benchmark, e.g. \"software engineer\", \"project manager\". Partial match against contract labor categories, which are free text, prefer a short phrase over a long one."
    • 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

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is free to add operational nuance — and it does: the price summary is computed across EVERY matching rate, not just the returned page, which prevents a real misinterpretation. It also flags that labor categories are free text and partial-matched. Missing: pagination/total-count behavior and any rate-limit or data-freshness notes.

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?

Front-loaded with the definition and purpose, then use cases, then return contents, then filters, then an example — a sensible information hierarchy with no filler. The quoted example questions add length but genuinely anchor the intended query shape rather than restating the tool name.

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 12-parameter, no-output-schema tool this is complete: it describes what each returned record contains (vendor name, contract number, SIN, education/experience requirements) and what the aggregate summary holds. An agent can call it correctly and interpret the response without further documentation.

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 baseline is 3; the description adds value by enumerating the filter axes (experience, education, worksite, business size, security clearance, price band) in one place and pairing them with a working example call. The subtle min_experience range-vs-exact-match caveat lives only in the schema, not the description, so it does not fully exceed the schema.

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?

States a specific verb and resource: GSA schedule hourly labor rates for a job title, defined precisely as "the ceiling rate vendors may charge the government under a GSA MAS contract." It also discloses the return shape (individual rates plus a min/p25/median/p75/max summary). It never names or contrasts with gsa_vendor_rates or gsa_rate_stats, so sibling differentiation is left implicit.

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 frames the use case with natural-language benchmark questions ("typical GSA hourly rate for a project manager") and gives a concrete invocation example with filters. It does not state when to prefer gsa_vendor_rates or gsa_rate_stats instead, so the routing decision is only partially supported.

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.