Skip to main content
Glama

DSSR posts in a country

get_dssr_locations_by_country
Read-onlyIdempotent

Returns the DSSR posts of a country by ISO alpha-2 code, each with its name and five-digit post code (external_id), as needed by the by-location and by-postcode tools. Use get_countries to resolve a name to the code. Returns no rates.

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_dssr_locations_by_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish a read-only, idempotent, non-destructive, closed-world operation. Beyond that, the description discloses the returned name and external_id fields, explains the identifier's downstream purpose, and explicitly excludes rates; only minor behaviors such as empty results or pagination remain unstated.

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 short sentences front-load the operation and then cover output identifiers, name resolution, and the rates exclusion. Every sentence contributes selection or invocation guidance with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup, the combined definition covers scope, code resolution, returned name and external_id fields, downstream use, and the absence of rates. Details such as empty-result or pagination behavior are not stated, but they are minor relative to the tool's apparent simplicity.

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 the schema already documents the ISO format, examples, the ZZ special case, and the get_countries workflow. The description repeats the alpha-2 requirement and resolution route but adds little input-specific meaning beyond that, so the high-coverage baseline 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?

The description uses a specific verb and resource—“Returns the DSSR posts of a country”—and scopes the lookup to an ISO alpha-2 code. The downstream by-location/by-postcode context and “Returns no rates” further distinguish it from rate-oriented siblings.

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?

It explicitly positions the tool as a prerequisite for by-location and by-postcode tools and directs agents to get_countries when starting with a country name. “Returns no rates” supplies a useful when-not boundary, although it does not name a specific rate-tool alternative.

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