Skip to main content
Glama

taufnaus Geschenke-Shop

Warenkorb

get_cart
Read-onlyIdempotent

Show the cart with current prices and availability.

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": {
      "cart_id": "<cart_id>"
    },
    "name": "get_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
cart_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description does add one piece of genuinely new context: prices and availability are current/live rather than cached. It says nothing about what happens if the cart_id is unknown or the cart has expired, which is the remaining behavioral gap.

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?

A single well-formed sentence with the resource and the freshness of the returned data front-loaded and no filler. It is efficient, though the brevity comes at the cost of the missing guidance noted elsewhere.

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?

With no output schema and rich annotations, the definition covers the safety profile and the freshness of prices, but for a lookup tool keyed on a single undocumented id it should say more about how to source cart_id and what an empty or expired cart yields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, cart_id, at 0% schema description coverage, so the description carries the full burden. "The cart" only loosely implies that the identifier selects a cart; nothing is said about its format, where to obtain it, or how an invalid id is handled.

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?

"Show the cart with current prices and availability" gives a specific verb (show) and resource (cart), and the read framing contrasts with the sibling set_cart. It stops short of naming alternatives, so the agent must infer that distinction from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states no conditions for when to call this versus set_cart or checkout, and no prerequisites such as a valid or non-expired cart. Usage is only implied by the word "Show".

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