Skip to main content
Glama

DSSR per diem by location post code

get_perdiem_allowance_by_postcode
Read-onlyIdempotent

Returns DSSR per diem (lodging, M&IE and maximum per diem in USD per day) for the post identified by its five-digit DSSR post code, today or on date. Every DSSR result carries the post code, so use it for follow-up lookups. Use get_perdiem_allowance_by_location for a name, get_perdiem_allowance for the whole country.

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

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.
postcodeYes5-digit DSSR post code (no zero-padding)
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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: which figures come back (lodging, M&IE, max per diem in USD/day) and the default-to-today behavior. It omits plan-tier date-range limits and the default verification_url link, though both are documented in the schema rather than the prose.

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 waste: the return payload and key input come first, followed by the sibling disambiguation and the follow-up-lookup note. No restatement of the title or schema fields.

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?

With no output schema, the description carries the burden of describing returns and does so concisely (lodging, M&IE, max per diem in USD/day). Combined with 100% schema coverage on the four parameters, an agent has what it needs to call this correctly; only edge behavior such as plan-tier date restrictions lives solely in the schema.

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 (date, postcode, country_iso_code, verification_url) is already fully documented with formats, ranges, defaults and the ZZ caveat. The description adds only the 'today when omitted' default, which the schema already states; baseline 3 applies when the schema does the heavy lifting.

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, maximum per diem in USD/day) for a post identified by its five-digit DSSR post code, today or on `date`. It also names the two sibling tools it is not (get_perdiem_allowance_by_location for name lookups, get_perdiem_allowance for whole-country), so an agent can pick it 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?

Explicit routing: use by-location when you only have a name, use get_perdiem_allowance for the whole country. It also adds a chaining hint — every DSSR result carries the post code, so this tool is the entry point for follow-up lookups — which is exactly the kind of when-to-use guidance that saves a round trip.

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