Skip to main content
Glama

AIFEC

checkout_set_shipping

Read-only

Choose the delivery option (carrier_id from checkout_shipping_options).

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": {
      "carrier_id": "<carrier_id>"
    },
    "name": "checkout_set_shipping"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrier_idYes
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The description says the tool 'chooses' a delivery option, i.e. it changes the cart's shipping selection, while annotations declare readOnlyHint=true, meaning the call does not modify state. State-mutating behavior is also implied by the session_id parameter, which exists to preserve 'the same cart between calls'. Nothing in the description discloses what changes, whether a prior selection is overwritten, or what the caller gets back.

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?

A single short sentence with the key parameter and its source front-loaded in parentheses; no filler or restatement of the tool name. Nothing could be removed without losing information.

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

Completeness2/5

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

For a checkout-step tool with no output schema and an annotation that misdescribes its effect, the description is too thin: it omits whether the selection persists, whether it must precede checkout_review/checkout_place, whether an existing selection is replaced, and what a caller sees on success. Only the parameter source is covered.

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 coverage is 50%: session_id is fully self-documented in the schema, and the description supplies the missing meaning for carrier_id by naming the tool that produces valid values (checkout_shipping_options). That provenance hint is real semantic value the integer 'minimum: 1' schema does not convey, though no example value or failure behavior is given.

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?

States a specific verb-plus-resource ('choose the delivery option') and ties the required carrier_id back to checkout_shipping_options, which distinguishes it from the options-listing sibling. It stops short of a fully explicit contrast with siblings like checkout_set_payment, but an agent can tell what this tool does.

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?

The parenthetical implies a prerequisite sequence (call checkout_shipping_options first to obtain a carrier_id), which is useful ordering guidance. However, there is no explicit when-to-use/when-not guidance, no statement that it replaces a prior selection, and no indication of where it sits relative to checkout_review or checkout_place.

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