Skip to main content
Glama

GS locality pay areas

get_opm_localities
Read-onlyIdempotent

Returns OPM General Schedule locality pay areas for the latest pay year with the code for get_opm_pay. location keeps areas whose name contains every word and areas of counties or cities with exactly that name (state narrows it); matched_places shows why. A place in no area returns Rest of U.S. (RUS); several areas come back when a name exists in several states or a city spans areas. Empty results mean an unknown name, not RUS. Territories are not covered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_opm_localities"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoRestrict `location` to one state.
locationNoCounty, city or locality area name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish a read-only, idempotent, non-destructive lookup, and the description adds substantial behavior beyond that: matching rules, latest pay year, RUS fallback, why `matched_places` exists, multiple-area results, and the important distinction between empty results and RUS. It also discloses that territories are not covered.

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?

The description is front-loaded with purpose, then moves through parameter semantics, fallback behavior, empty-result interpretation, and coverage limits. Every sentence carries useful information, and there is no redundant restatement of the schema or title.

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 two-parameter lookup with rich annotations and no output schema, the description is complete enough to call correctly. It covers filtering behavior, RUS fallback, multiple matches, empty results, and territorial coverage gaps, leaving no major operational ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is already 100%, the description adds meaningful matching semantics beyond the schema: `location` keeps locality-area names containing every word and county/city names with exactly that name, while `state` narrows the lookup. This is the kind of non-obvious filtering behavior an agent needs in order to use the parameters correctly.

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?

The description states a specific verb and resource: it returns OPM General Schedule locality pay areas for the latest pay year and includes the code needed by get_opm_pay. That clearly separates it from get_opm_pay, but it does not explicitly distinguish itself from the close sibling get_opm_locality_by_county.

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?

It gives clear operational context for `location` and `state`, including edge cases such as RUS fallback, multiple matches, empty results, and uncovered territories. It does not explicitly say when to use this tool instead of get_opm_locality_by_county or search_opm_pay, so the sibling routing remains implicit.

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