Skip to main content
Glama

Search GS pay by locality area

search_opm_pay
Read-onlyIdempotent

Return the latest General Schedule pay tables whose locality area matches every word of q: each word must be contained in the area name, case-insensitively, or equal its code. grade and step narrow the rates; no match returns an empty results list. Matching only looks at OPM's area names, not the counties and towns they cover, so a town missing from the names returns nothing, which does not mean Rest of U.S. Use get_opm_localities to resolve a place to its area.

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": {
      "q": "<q>"
    },
    "name": "search_opm_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords to find in the locality area name or code, all required, case-insensitive.
stepNoReturn only this step, 1 to 10.
gradeNoReturn only this GS grade, 1 to 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: AND-across-words matching, case-insensitivity, an empty result on no match, and the caveat that matching covers only OPM area names, not counties or towns, so an empty result does not imply Rest of U.S. It stops short of describing the shape of each results row, which keeps it off a 5.

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 description is front-loaded with the matching rule, then the filters, then the empty-result semantics, then the caveat and the alternative. That ordering is sensible and sentence packed. It is dense and slightly long, but no sentence is filler.

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 three-parameter, fully documented read tool with rich annotations and no output schema, the description covers matching logic, the empty-result behavior, a known coverage gap, and routing to the sibling resolver. An agent has everything it needs to call this correctly and to interpret an empty response.

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. The description nevertheless sharpens `q`: every word must appear in the area name, or the word must equal the area code, which is more precise than the schema's "all required" phrasing. It also states that `grade` and `step` narrow the rates, which ties those filters to output rather than just range limits.

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 names a specific verb and resource ('Return the latest General Schedule pay tables') and scopes it to locality-area matching on `q`. It is clearly separable from get_opm_pay and get_opm_localities, since the latter is explicitly named as the resolver for places.

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 states when the tool applies ('matches every word of q'), names the alternative for a different need ('Use get_opm_localities to resolve a place to its area'), and warns about a false-negative condition. It even says no match returns an empty `results` list, so the agent knows what an empty result means.

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