Skip to main content
Glama

Gsa Rate Stats

gsa_rate_stats
Read-onlyIdempotent

Price statistics only for a GSA schedule labor category, min, 25th percentile, median, 75th percentile and max hourly ceiling rate across every matching contract rate, with no individual rows. Use when you want the benchmark number rather than the listings: "what is the median GSA rate for a business analyst", "p75 hourly rate for cybersecurity engineers with a clearance". Same filters as gsa_labor_rates. Example: gsa_rate_stats({ labor_category: "project manager", education: "BA", min_experience: 10 })

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": {
      "education": "bachelors",
      "labor_category": "project manager"
    },
    "name": "gsa_rate_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. "project manager".
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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: results are aggregated over 'every matching contract rate' and contain no individual rows, and it names the output statistics returned. It stops short of describing the response envelope (field names, count of matches, units), which matters slightly more since no output schema exists.

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 purpose and the 'statistics, not rows' distinction are front-loaded in the first sentence, followed by usage guidance and a concrete example — a sensible ordering. The quoted example queries are slightly wordy but each earns its place by demonstrating the kind of question the tool answers.

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 an 11-parameter, read-only aggregation tool with full schema coverage and annotations but no output schema, the description supplies the essentials: what is aggregated, what statistics come back, how it differs from the listings sibling, and an example invocation. Missing only the shape of the returned object, which would be a nice-to-have given there is no output schema.

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% and the parameter descriptions already explain enums, plain-spelling aliases and the min_experience range semantics, so the description adds little per-parameter meaning. Its main contribution is the statement that filters are identical to gsa_labor_rates plus a worked example call combining labor_category, education and min_experience — helpful but marginal against a fully documented schema.

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 — price statistics for a GSA schedule labor category — and enumerates exactly which statistics are returned (min, p25, median, p75, max hourly ceiling rate). It explicitly distinguishes itself from the listing sibling by noting 'no individual rows' and 'Same filters as gsa_labor_rates', so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit selection rule: 'Use when you want the benchmark number rather than the listings', which routes the agent away from the row-level sibling. Two concrete natural-language query examples ('what is the median GSA rate for a business analyst', 'p75 hourly rate for cybersecurity engineers with a clearance') make the intended trigger unambiguous.

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.