Skip to main content
Glama

AIFEC

checkout_shipping_options

Read-only

The delivery options for the order with their price and delay, and the one selected. Needs the delivery address first.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so safety is already covered. The description adds the meaningful prerequisite that a delivery address must exist first, but it does not explain failure behavior, whether the selected option can be null, or any side effects beyond the read-only annotation.

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?

Two short sentences, with the returned content front-loaded and the prerequisite immediately after. It could be tighter by using a direct verb such as 'List,' but it has no extraneous wording.

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 simple read-only checkout tool with one optional parameter and no output schema, the description is nearly complete: it says what is returned and the key prerequisite. It stops short of explaining how the selected option is represented or what happens if no address is set.

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?

There is one optional session_id parameter with 100% schema coverage; the schema explains its purpose and header fallback. The description does not add any parameter-specific meaning, so the baseline score of 3 applies.

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 the resource (delivery options for the order) and the data returned (price, delay, selected option). It distinguishes this from checkout_set_shipping by framing it as the options list, though it uses a noun phrase rather than an explicit verb.

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 only usage guidance is the prerequisite 'Needs the delivery address first,' which implies calling it during checkout after address entry. It does not explicitly say when to use this versus checkout_set_shipping or shipping_quote, nor does it state when not to call it.

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