Skip to main content
Glama

Moqway

List shipping options

list_shipping_options
Read-onlyIdempotent

Shipping services and incoterms available to a destination country (ISO-2), with transit days and per-kg rates. DDP options include import duty.

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": "<country>"
    },
    "name": "list_shipping_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is narrower and it adds real value by disclosing what comes back: service list, incoterms, transit times, per-kg rates, and that DDP options bundle import duty. It stops short of covering currency or freshness/caching of the rates.

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?

Two short sentences, zero filler, with the core resource and its key filter front-loaded and the return payload details following. Nothing is repeated from annotations or schema.

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?

For a single-parameter, read-only lookup with no output schema, the definition covers input meaning and the shape of the result well enough to call it correctly. Minor gaps remain, notably the currency of the per-kg rates and how many options to expect.

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 description coverage is 0% and the schema only constrains country to a 2-character string with no meaning attached. The description compensates by declaring the intended format as ISO-2 and framing it as the destination country, which is the meaning an agent needs to populate it correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (shipping services and incoterms) scoped to a destination country and states the payload contents (transit days, per-kg rates, DDP duty inclusion). It is clearly distinguishable from order/product/supplier siblings by domain, but it does not explicitly contrast with any named sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'available to a destination country', which tells the agent this is a lookup keyed on a country. There is no explicit when-to-use versus alternatives and no stated preconditions or exclusions.

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