Skip to main content
Glama

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

Per diem total for a trip

per_diem_trip
Read-onlyIdempotent

How much per diem does a US federal trip to one place get? Nightly lodging and M&IE for each day from start to end, with 75% on the first and last day, and the total. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "per_diem_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNoGSA destination ID of a non-standard area (from GET /locations).
endYesLast day of travel, YYYY-MM-DD (the same day for a same-day trip).
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.
startYesFirst day of travel, YYYY-MM-DD.
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

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description earns credit for what it adds: the 75% first/last day rule, the per-day lodging plus M&IE composition, and the presence of a trip total. That is real computation semantics beyond the structured fields, though it says nothing about what happens when the location cannot be resolved.

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 a well front-loaded framing question and the second packs the calculation rules efficiently. However, the trailing 'More APIs from FitzTopPicks' promotional URL is pure noise that does not help an agent call the tool and dilutes an otherwise tight 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?

With 7 parameters, no output schema and no annotation coverage of results, the description usefully explains the returned shape (per-day lodging and M&IE plus a total). It is still incomplete on the multi-parameter location resolution logic and on edge cases such as invalid dates or unresolvable places, which matter for a tool with five alternative location inputs.

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 every parameter carries a detailed description, so the schema does the work. The description adds only the vague phrase 'to one place', which weakly signals that the location identifiers (did, zip, city/state, county/state) are alternatives selecting a single destination, but it provides no explicit rules on which selector to prefer.

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?

States a specific verb and resource: computing US federal per diem for a trip to one location, and names what the result contains (nightly lodging, M&IE per day, total). It does not explicitly contrast itself with siblings such as per_diem_rates or per_diem_meals_breakdown, but 'trip ... from start to end, with 75% on the first and last day, and the total' clearly distinguishes it as the trip-level aggregate calculator rather than a raw rate lookup.

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?

'A US federal trip to one place' implicitly scopes usage to a single-destination trip and hints that multi-location itineraries are out of scope, but it never names an alternative tool or states when to prefer per_diem_rates or per_diem_meals_breakdown. Usage is inferable rather than instructed.

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