Skip to main content
Glama

Kargom

Prepare shipment for approval

prepare_shipment
Idempotent

Saves the chosen quote as a shipment waiting for the user’s approval and returns an approval link on kargom.com. Nothing is charged and no label is created until the user opens the link, checks the details and pays there (Kargom balance or card). The user needs this link to approve. Same quote_id twice returns the same link. Use get_shipment with the returned approval_id to see if it was approved.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "prepare_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesquote_id from quote_shipment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the critical non-obvious behavior: nothing is charged and no label is created until the user opens the link and pays externally, so this is a soft reservation rather than a booking. It also explains retry semantics ('Same quote_id twice returns the same link'), which corroborates idempotentHint and tells the agent retrying is safe. It states exactly what is returned (approval link, approval_id) and who must act next (the user).

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?

Front-loaded with the action, followed by the payment/label caveat and the retry and follow-up notes, in a logical order with no padding. Slight redundancy in 'The user needs this link to approve,' which restates the opening sentence's approval framing.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description covers everything an agent needs: what is created, what it is not (no charge, no label), that the result is idempotent, how to retrieve the link/approval_id, and how to poll approval status. Nothing material is missing.

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 only one parameter and the schema already documents it at 100% coverage, including the max length and its source (quote_shipment). The description adds idempotency semantics keyed on quote_id, but no format or validation detail beyond what the schema supplies, so the baseline 3 applies.

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 opens with a specific verb and resource ('Saves the chosen quote as a shipment waiting for the user's approval') and names the concrete artifact produced ('an approval link on kargom.com'). It also distinguishes itself from the follow-up tool by pointing at get_shipment for status checks, so an agent can separate it from quote_shipment and get_shipment without opening any schema.

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?

Usage context is clear: call this after choosing a quote, and the returned approval_id is the handle for checking approval via get_shipment. The prerequisite chain (quote_id comes from quote_shipment) is implied rather than spelled out, and no explicit when-not-to-use case or alternative is named, keeping it below a 5.

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