Skip to main content
Glama

Kargom

Get shipment prices

quote_shipment
Read-only

Real prices for a domestic shipment from the user’s saved sender address to a recipient. Returns options with a quote_id each; a quote_id is valid for about 15 minutes, then call quote_shipment again. Nothing is charged.

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": {
      "recipient": "<recipient>"
    },
    "name": "quote_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
desiNoDesi (Turkish volumetric weight = length×width×height cm / 3000). Sellers often give only desi; then weight and size are not needed
contentsNoWhat is inside (optional)
width_cmNoWidth in cm
height_cmNoHeight in cm
length_cmNoLength in cm
recipientYes
weight_kgNoWeight in kg
sender_address_idNoSaved sender address id from get_account. Default: the first one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description still adds real value beyond them by disclosing the ~15-minute quote_id lifetime and that 'Nothing is charged.' It does not say whether quoted prices are guaranteed at booking time, which would matter for a pricing tool.

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?

Three short sentences, front-loaded with what is returned, followed by the validity constraint and the no-charge assurance. No sentence is filler and the most decision-relevant facts come first.

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 an eight-parameter tool with a nested recipient object and no output schema, the definition covers the essential contract: options with quote_id values, expiry, and absence of charge. It stops short of describing the pricing option fields an agent would need to compare, but the schema carries most parameter burden.

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 description coverage is 88%, so the parameters are already well documented, including the desi-vs-weight/size tradeoff and the sender_address_id default. The description adds only the framing that pricing originates from the user's saved sender address, which is a marginal but real clarification; baseline 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?

States a specific verb and resource: 'Real prices for a domestic shipment from the user's saved sender address to a recipient.' An agent can tell this is a pricing/quoting operation rather than a booking operation, but the description never distinguishes it from the sibling get_shipping_prices, which reads like it does the same thing.

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?

It gives one concrete re-invocation rule ('a quote_id is valid for about 15 minutes, then call quote_shipment again'), which is genuinely useful. However, there is no guidance on when to call this versus get_shipping_prices, prepare_shipment, or get_shipment, so the selection decision between near-identical siblings is left to inference.

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