Skip to main content
Glama

Utility: List Countries

list_supported_countries
Read-onlyIdempotent

[Utility] [What it does] Lists countries currently supported by DSers, returning each country's ID, code, and display name. [When to use] Use it to obtain valid destination country codes before calling logistics tools such as list_platform_shipping_methods. [When not to use] It does not support search, filtering, or pagination, and cannot modify country configuration. [How to use] No input is required. Copy the returned countries[].code exactly for later logistics calls; never use the country name or ID as the code. total equals the number of countries returned in this call. [Side effects] None; read-only. [Confirmation] Not required.

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": "list_supported_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of countries returned
countriesYesCountries returned by DSers Infra BFF in upstream order
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the "[Side effects] None; read-only" line is largely redundant. What the description does add beyond structured data is the absence of search/filter/pagination and the meaning of `total` as the count returned in this call. That is real behavioral context, but the annotation overlap keeps it short of a 5.

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?

Bracketed section labels make it scannable and the critical warning (use code, not name or ID) is placed in the how-to-use block where it will be read. The labels and the side-effects/confirmation lines cost tokens for little gain given the annotations, so it is slightly over-structured rather than maximally tight.

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 zero-parameter read-only list tool with an output schema and full annotation coverage, everything an agent needs is present: when to call it, what it cannot do, and the one field-usage trap (code vs. name/ID). An output schema exists, so the description is not obligated to enumerate return values further.

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?

Zero parameters, so the baseline is 4. The description correctly states no input is required, and its guidance about copying `countries[].code` verbatim rather than using the name or ID adds value that the empty schema cannot convey.

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 ("Lists countries currently supported by DSers") and names the exact fields returned (ID, code, display name). The "[Utility]" tag plus the explicit tie to logistics tooling makes it distinguishable from the sibling list_* tools at a glance.

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 explicit when-to-use (obtain valid destination country codes before logistics calls), names the concrete downstream sibling list_platform_shipping_methods, and adds a when-not-to-use clause (no search, filtering, pagination, no config changes). Nothing is left to inference.

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.