Skip to main content
Glama

Supplier: List Logistics by Country

list_platform_shipping_methods
Read-onlyIdempotent

[Supplier / Logistics] [What it does] Lists logistics/shipping services available for one supplier platform and destination country (or Global). [When to use] Use when you need valid shipping_method values for a given supplier and destination, such as before update_order_supplier or a pricing calculation. [When not to use] Not for checking an order's actual shipping status; this only returns available service options. [How to use] supplier_platform_id (from list_stores) and country_code (from the countries list, a 2-3 letter code or "Global") are both required; returns each service's ID, name, average cost, and time. [Side effects] None; read-only. [Confirmation] Not required.

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": {
      "supplier_platform_id": "<supplier_platform_id>",
      "country_code": "<country_code>"
    },
    "name": "list_platform_shipping_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesRequired two- or three-letter countries[].code returned by list_supported_countries. Global is allowed only for an explicitly global query.
supplier_platform_idYesRequired supplier platform ID. Copy the exact supplier_platform_id from list_stores supplier_apps[].

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of logistics services returned
logisticsYesAvailable logistics services in DSers 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.1/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 the '[Side effects] None; read-only' and '[Confirmation] Not required' lines largely restate structured data. The useful additions are the note that only currently available service options are returned and what each service carries (ID, name, average cost, time) — but with an output schema present, that is partially duplicated too.

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?

It is well front-loaded with labelled sections that map cleanly to an agent's decision sequence (what / when / when not / how / side effects). It is somewhat longer than needed for a two-parameter read-only list tool, with the side-effects and confirmation lines adding bulk beyond what the annotations already state.

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?

Given two required parameters, full schema coverage, four annotations, and an existing output schema, the description covers purpose, routing, prerequisites and exclusions adequately. Return-field explanations are optional here because the output schema carries them, so nothing an agent needs in order to call correctly is missing.

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 the schema already explains both parameters, including the 2-3 letter code format, the 'Global' allowance, and where to copy supplier_platform_id from. The description's '[How to use]' line repeats those same sourcing hints, adding little beyond the schema.

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 names a specific verb and resource — 'Lists logistics/shipping services available for one supplier platform and destination country (or Global)' — and scopes it to availability rather than order status. The explicit exclusion of 'an order's actual shipping status' separates it from status-lookup siblings without needing to open their schemas.

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?

Provides an explicit when-to-use ('need valid shipping_method values ... before update_order_supplier or a pricing calculation') and an explicit when-not-to-use (checking an order's actual shipping status). It also points to prerequisite tools (list_stores, the countries list) so the agent can resolve inputs before calling.

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.