Skip to main content
Glama

AIFEC

shipping_quote

Read-only

Delivery options, prices and times to a destination. Give the postcode (and the 2-letter country if it is not the shop's own). Quotes the product given, or the current cart when no product is given.

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

Input Schema

NameRequiredDescriptionDefault
qtyNo
countryNoISO 3166-1 alpha-2 code, for example ES
postcodeNo
product_idNo
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.
variant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a non-mutating operation, so the description is not required to establish safety. It adds useful behavior context: quoting is destination-driven and resolves against a product or the current cart, which explains why the call can succeed with no parameters. It does not disclose error behavior for invalid postcodes or unsupported countries, nor how prices are sourced, which would be the remaining valuable additions.

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?

Three short sentences, front-loaded with what the tool returns, then input requirements, then quoting semantics. No filler. The phrase 'Quotes the product given' is slightly awkward and requires the reader to infer 'product_id', a minor clarity cost.

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

Completeness3/5

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

For a six-parameter, all-optional tool with no output schema, the description covers the core behavior and the two most important inputs. It omits what happens when no postcode is supplied, and leaves qty and variant_id unexplained, both of which affect the quote returned. Adequate but not complete.

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?

With schema coverage at 33%, the description must carry weight, and it does explain postcode, country (as a 2-letter code only needed for non-domestic destinations), and product_id (product quote vs cart quote). It says nothing about qty, variant_id, or session_id, so three of six parameters rely entirely on schema text, and qty/variant_id have no descriptions at all. The description partially compensates but leaves real gaps.

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 first sentence names the resource precisely (delivery options, prices, times) and the third specifies the quoting basis, so an agent knows this returns shipping quotes rather than performing checkout. The verb is only implicit in the opening line ('Delivery options, prices and times') and is clarified later by 'Quotes the product given, or the current cart'. It does nothing to distinguish itself from the sibling checkout_shipping_options, leaving that differentiation to the agent.

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?

'Give the postcode (and the 2-letter country if it is not the shop's own)' tells the agent what input context is needed, and the product-vs-cart sentence indicates when to pass product_id. However, there is no statement of when to prefer this over checkout_shipping_options, check_availability, or cart_view, and no guidance on prerequisites such as having items in the cart. Usage is therefore implied rather than explicitly scoped.

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