Skip to main content
Glama

DSSR per diem by country

get_perdiem_allowance
Read-onlyIdempotent

Returns State Department (DSSR) per diem for every post in a country: lodging, M&IE and maximum per diem in USD per day, today or on date. For one post use get_perdiem_allowance_by_location or get_perdiem_allowance_by_postcode; for a place name without a country code use search_perdiem. For Department of Defense travel use get_dtmo_perdiem_oconus.

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": {
      "country_iso_code": "<country_iso_code>"
    },
    "name": "get_perdiem_allowance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day the rates must be in force, YYYY-MM-DD; today when omitted. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date.
country_iso_codeYesISO 3166-1 alpha-2 country code, e.g. PG for Papua New Guinea; ZZ stands for 'Other Foreign Localities', not a country. Resolve a country name to its code with get_countries (q=name).
verification_urlNoIncluded by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Specific date in YYYY-MM-DD format"New value: +"The day the rates must be in force, YYYY-MM-DD; today when omitted. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date."
  2. Changed2 schema fields changed
    • changedInput schema / properties / verification_url / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / verification_url / description
      Previous value: -"If 'True', will include a verification url in the payload, pointing to the official government source. This is useful to crosscheck that the API returns the proper data and for auditing."New value: +"Included by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it."
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that rates are USD per day and reflect 'today or on date', but that mostly restates the schema's date parameter; it adds nothing about coverage gaps (e.g. posts missing from a country) or result ordering/volume. With annotations doing the heavy lifting, this is adequate but not rich.

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

Conciseness5/5

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

Three sentences, zero filler: the return content and scope lead, then the routing alternatives follow. Every clause either describes output or dispatches to a sibling.

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?

There is no output schema, and the description compensates by naming the fields returned (lodging, M&IE, maximum per diem, currency, per-day basis) and the temporal default, which is enough to call it correctly. Minor gaps remain around result granularity per post and missing-location behavior, but the definition is sufficient for a simple read 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 already documents the ISO code format, the ZZ special case, the date plan limits and the verification_url default, so the schema carries parameter meaning. The description only echoes 'today or on `date`' and does not add syntax or behavioral nuance beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns State Department (DSSR) per diem for every post in a country') and enumerates the returned fields (lodging, M&IE, maximum per diem in USD/day). It explicitly distinguishes itself from get_perdiem_allowance_by_location, get_perdiem_allowance_by_postcode, search_perdiem and get_dtmo_perdiem_oconus, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the when-to-use condition (all posts in a country) and three explicit alternatives with the condition that selects each: one post by location or postcode, place name without a country code, and DoD travel. This is the when/when-not/alternatives pattern at full strength.

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