Skip to main content
Glama

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

Hotel tax exemption for government cards

per_diem_tax_exempt
Read-onlyIdempotent

Is a government travel card exempt from hotel or sales tax in a US state, and which form to show? From GSA SmartPay. 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_tax_exempt"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNoWith state: only this card type's forms.
stateNoTwo-letter code or name of a state, DC or territory (PR, GU, VI, AS, MP).
exemptNoWithout state: iba (states that exempt individually billed travel cards), cba, or none.

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 useful provenance (GSA SmartPay as the authoritative source) and signals that results include a form to show, but says nothing about coverage gaps, territory handling, or how results are shaped. It does not contradict the annotations.

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 sentence is front-loaded and tight, stating the question the tool answers immediately. The second sentence is a promotional link for unrelated APIs that does not help an agent select or invoke this tool and dilutes the 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 no output schema and all parameters optional, the description should clarify what happens with zero arguments and what a result contains (exemption status, form name/number, per-state variance). It gestures at the return content with 'which form to show' but leaves the empty-argument behavior and result shape to inference.

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 all three parameters — including the state-vs-exempt mode distinction and enum meanings — are already documented in the schema at the level of detail the description provides. The description adds no syntax, defaults, or interaction rules beyond that, so baseline 3 applies.

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 concrete verb-like outcome — determining whether a government travel card is exempt from hotel or sales tax in a US state, and which form to present — plus the data source (GSA SmartPay). That is specific enough to distinguish it from the sibling per_diem_rates, per_diem_locations and per_diem_meals_breakdown tools, though it is phrased as a question rather than a direct statement of operation.

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 question framing: an agent can infer it is for checking tax-exemption status and required paperwork. There is no explicit when-to-use or when-not-to-use guidance, and no naming of an alternative tool for related questions such as rates or per-diem amounts.

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