Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

US federal per diem rates for a place

per_diem_rates
Read-onlyIdempotent

What are the GSA per diem rates (lodging and meals & incidentals) for a US city, county or ZIP on a date or for a fiscal year? More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": "per_diem_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
fyNoFiscal year (2026 or 2027) instead of a date: no single-day rate, all months.
didNoGSA destination ID of a non-standard area (from GET /locations).
zipNo5-digit ZIP code (ZIP+4 is fine), as a string. Follows GSA's ZIP code file.
cityNoCity or town (with state). A GSA destination name, a GSA city-limits area, or any Census place; a place GSA does not name gets its county's rate.
dateNoYYYY-MM-DD, from 2025-10-01 to 2027-09-30 (FY2026-FY2027). Default: today.
stateNoTwo-letter code or name (with city or county). CONUS only: the 48 contiguous states and DC.
countyNoCounty, parish or Virginia independent city (with state): "Fairfax", "Fairfax County", "City of Richmond".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the domain framing (lodging vs meals & incidentals, GSA as the authority); it says nothing about default behavior when no location is supplied, multi-selector precedence, or result shape. The second sentence is promotional boilerplate, not behavioral information.

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

Conciseness3/5

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

The core is a single sentence, but it is phrased as a question rather than a declarative statement of function, which is slightly less direct for tool selection. The trailing 'More APIs from FitzTopPicks' link with UTM parameters is pure promotion and does not earn its place in a tool definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only lookup with rich annotations and a fully documented schema does not need much prose, so the description is adequate. What it omits is guidance on choosing among the several mutually redundant location selectors and on what happens with zero parameters — the most likely sources of a mis-call for this tool.

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 description coverage is 100%, and the schema already explains each of the seven parameters in detail, including the FY-vs-date tradeoff, ZIP+4 handling, CONUS limitation, and county naming forms. The description merely lists the selector families the schema documents, adding no semantics of its own (e.g., how city+state vs zip vs did interact). Baseline 3 is warranted.

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 names a specific resource and scope: GSA per diem rates, broken out as lodging and meals & incidentals, for a US city, county or ZIP, for a date or fiscal year. It is clear what the tool returns, but it never distinguishes itself from close siblings such as per_diem_meals_breakdown or per_diem_locations, so the agent gets no explicit routing signal.

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?

Usage is only implied by the wording 'for a US city, county or ZIP on a date or for a fiscal year' — the reader must infer that this is the go-to tool for a single-place rate lookup. There is no explicit 'use this when', no exclusion, and no mention of when to prefer the sibling breakdown or locations tools.

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