Skip to main content
Glama

Set shipping method

set_shipping_method
Idempotent

Choose a shipping method by its option_id (from get_shipping_options). Args: option_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
option_idNoShipping option id from get_shipping_options (currently 'worldwide').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
errorNoUnknown option_id or empty cart.
shipping_methodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / option_id / description
      Added value: +"Shipping option id from get_shipping_options (currently 'worldwide')."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "error": {
      +      "description": "Unknown option_id or empty cart.",
      +      "type": "string"
      +    },
      +    "ok": {
      +      "type": "boolean"
      +    },
      +    "shipping_method": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds little beyond stating the action, but does not contradict annotations. It lacks details on error handling or effects.

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 concise sentences that front-load the action and immediately convey the purpose. No superfluous information.

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 the tool's simplicity (one parameter, output schema present), the description is nearly complete. It could mention that setting is idempotent or that the option_id must be valid, but the annotations cover idempotency.

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 provides a detailed description of option_id. The description merely repeats 'option_id' without adding new meaning, so baseline 3 is appropriate.

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 clearly states the action (choose) and the resource (shipping method), referencing the source tool get_shipping_options. This distinguishes it from sibling tools like get_shipping_options.

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

Usage Guidelines4/5

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

The description implicitly guides usage by requiring option_id from get_shipping_options, but does not explicitly state when to use or not use this tool versus alternatives. Still clear enough for a simple setter.

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