GSA Per Diem

compare_locations

Read-only

Compare per diem rates across multiple locations.

locations: list of {"city": "...", "state": "XX"} dicts (optionally
with "county"), max 25 entries. Returns rates sorted by max daily
total (highest first). Ambiguous or unresolved cities are listed with
their status and candidate rate areas instead of a rate.

Useful for travel IGCE development when comparing destination costs.

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": {
      "locations": "<locations>"
    },
    "name": "compare_locations"
  }
}

Input Schema

Name	Required	Description	Default
`locations`	Yes
`fiscal_year`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds substantive behavior: a 25-entry cap and, importantly, that ambiguous/unresolved cities come back as status entries with candidate areas instead of a rate, which prevents the agent from misreading a 'no rate' result as an error.

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?

Front-loads the purpose, then details the input shape and the return/ambiguity behavior in tight sentences. The trailing IGCE sentence is somewhat redundant with the opening claim but adds domain context cheaply; nothing bloats it.

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?

An output schema exists, so return-value explanation is bonus rather than required, yet the description usefully notes sorting by max daily total and the ambiguous-city status shape. The main gap is the unmentioned fiscal_year parameter; otherwise the definition is sufficient to invoke correctly.

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 0%, so the description must compensate. It documents the 'locations' array item shape ('city', 'state', optional 'county') and the 25-entry max, which is genuinely useful. However, the 'fiscal_year' parameter is not mentioned at all, leaving one of two parameters undocumented.

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?

Opens with a specific verb and resource: 'Compare per diem rates across multiple locations.' An agent can tell this is a multi-location comparison operation. It does not explicitly name siblings like lookup_city_perdiem or lookup_zip_perdiem, so differentiation is left to inference.

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?

'Useful for travel IGCE development when comparing destination costs' gives a context for use but no explicit when-not guidance or alternative routing. An agent must infer that single-location lookups belong to lookup_city_perdiem rather than being told.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GSA Per Diem tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.