Skip to main content
Glama

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

Non-standard per diem areas

per_diem_locations
Read-onlyIdempotent

Which US places have their own (non-standard) GSA per diem rate, by state or search, with destination IDs and the counties they cover. 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_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch text (part of a name, county or city).
fyNoFiscal year (default: the current one).
limitNo1-100 (default 25).
stateNoTwo-letter code or name.
offsetNoFor paging (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 covered. The description contributes the useful detail that results include destination IDs and county coverage, but says nothing about result volume, ordering, or what happens when a state has no non-standard areas.

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 first sentence is dense and front-loaded with the resource and return content. The second sentence is a promotional link to the vendor's other APIs that does not help an agent select or invoke this tool, and it dilutes an otherwise tight definition.

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?

For a read-only, five-optional-parameter lookup with no output schema, the description covers what the tool returns (places, destination IDs, county coverage) and how it can be narrowed. Only the absence of guidance on when to prefer sibling per diem tools keeps it from a 5.

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%, so every parameter (q, fy, limit, state, offset) is already documented in the schema. The description only reinforces that state and search are the two filtering axes, adding no syntax, format, or interaction detail beyond that baseline.

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 resource and scope: US places with their own non-standard GSA per diem rate, returned with destination IDs and covered counties. That is clearly distinct from per_diem_rates or per_diem_meals_breakdown. It lacks an explicit leading verb ('Which US places have...' is descriptive rather than action-oriented), which keeps it just short of a 5.

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?

The phrase 'by state or search' implies the two main retrieval modes but never states when to choose this tool over per_diem_rates, nor any prerequisites or exclusions. Usage is inferable from the resource name but not spelled out.

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