Skip to main content
Glama

GS locality pay area of a county

get_opm_locality_by_county
Read-onlyIdempotent

Returns the General Schedule locality pay area of a county by five-digit FIPS code for the latest pay year, with the code for get_opm_pay. Counties outside every area return Rest of U.S. (RUS); every county in Alaska or Hawaii returns that state's area. Unknown codes, Connecticut planning regions and territory counties are 404 errors. Use get_opm_localities to search by name.

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": {
      "fips": "<fips>"
    },
    "name": "get_opm_locality_by_county"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsYesFive-digit county FIPS code: two for the state and three for the county.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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, closed-world), so the marginal bar is low, yet the description still adds real behavior: the RUS fallback for uncovered counties, the blanket Alaska/Hawaii state-area rule, and the 404 families. It stops short of saying whether the result is cached or versioned by pay year, but the coverage is well above the annotation baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the return value, then edge-case behavior, then the sibling routing. No restatement of the title and no filler; every clause carries a distinct fact.

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?

With a single required parameter, full schema coverage, and no output schema, the description must carry return semantics and does: it says a pay area is returned plus an associated get_opm_pay code, and defines fallback cases. It could be slightly sharper about the exact response fields (area name vs. code), but nothing needed to call it correctly is missing.

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 fips property already explains the two-state/three-county breakdown and gives an example, so the description's "five-digit FIPS code" adds no new meaning for the input. The mention of "the code for get_opm_pay" is about the response, not the parameter, so baseline 3 applies.

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?

States a specific verb and resource ("Returns the General Schedule locality pay area of a county"), the input form (five-digit FIPS), the temporal scope (latest pay year), and an extra output linkage (the code for get_opm_pay). Combined with the sibling it explicitly disclaims (get_opm_localities for name search), an agent can pick it without opening the 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?

Names the alternative lookup tool and the condition that selects it ("Use get_opm_localities to search by name"), which is exactly the inverse of this tool's FIPS-only input. It also pre-empts misuse by stating which inputs are guaranteed 404s (unknown codes, Connecticut planning regions, territory counties).

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