Skip to main content
Glama

DSSR per diem by location name

get_perdiem_allowance_by_location
Read-onlyIdempotent

Returns DSSR per diem (lodging, M&IE and maximum per diem in USD per day) for one post in a country matched by name, case-insensitive and partial, today or on date. Find exact post names with get_dssr_locations_by_country or search_perdiem. Use get_perdiem_allowance for the whole country, get_perdiem_allowance_by_postcode for a known post code.

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

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.
locationYesLocation name, case insensitive
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.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower; the description adds useful context by explaining that matching is case-insensitive and partial and that the default date is today. It does not mention plan-based date limits, though the schema's date property does, and it says nothing about no-match behavior.

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

Conciseness4/5

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

Three sentences, front-loaded with the return payload, then discovery of post names, then routing to siblings. Every clause adds information, but the first sentence is long enough that the maximum per diem figure and the name-matching rule compete for attention.

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, so the description correctly spells out what comes back (lodging, M&IE, and maximum per diem in USD per day), and it covers name-matching behavior plus sibling routing. It leaves minor gaps around empty results and the bundled verification_url flag, which the schema handles on its own.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying partial (not just case-insensitive) name matching, and it points to get_dssr_locations_by_country or search_perdiem when the location name is uncertain, which explains how to resolve the required location and country_iso_code pair.

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 DSSR per diem (lodging, M&IE, and maximum) for a single post, matched by name. It explicitly distinguishes itself from get_perdiem_allowance (whole country) and get_perdiem_allowance_by_postcode (known code), so an agent can separate it from its many siblings 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?

Names three alternatives and the exact condition that selects each: get_dssr_locations_by_country or search_perdiem to find exact post names, get_perdiem_allowance for a country-wide answer, and get_perdiem_allowance_by_postcode when a post code is known. This states both when to use this tool and when to use a different one.

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