Skip to main content
Glama

GS pay by locality code

get_opm_pay
Read-onlyIdempotent

Return the latest pay table of a locality pay area, ordered by grade and step, or 404 for an unknown code. grade and step narrow the rates. Use GS for the base table without locality pay, and RUS for Rest of U.S.

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": {
      "locality_code": "<locality_code>"
    },
    "name": "get_opm_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNoReturn only this step, 1 to 10.
gradeNoReturn only this GS grade, 1 to 15.
locality_codeYesOPM locality pay area code, from /v1/opm/localities, or GS for the base table. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavior beyond them: results are the latest table, sorted by grade then step, and an unknown code yields a 404 rather than an empty set.

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?

Two compact sentences, front-loaded with what is returned and its ordering, followed by the filtering and sentinel-value notes. No filler, though the sentinel guidance could be folded in more tightly with the first 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 single-lookup read tool with no output schema, the description covers what comes back, how it is ordered, how to filter, and the failure mode. The absence of return-field detail is acceptable since the caller mainly needs the table itself.

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 the baseline is 3, but the description adds meaning the schema lacks — notably the RUS sentinel value and the fact that GS selects the locality-free base table. It also clarifies that grade and step act as narrowing filters on the returned table.

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: 'Return the latest pay table of a locality pay area, ordered by grade and step.' That is clearly distinct from lookup-style siblings like get_opm_localities, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Gives useful conditional guidance for the locality_code value ('Use GS for the base table without locality pay, and RUS for Rest of U.S.') and for narrowing with grade/step. It does not say when to reach for this tool instead of search_opm_pay or get_opm_localities, so cross-tool routing is left implied.

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.

Resources