Skip to main content
Glama

Storewire Lite demo store

View a cart

cart_view
Read-onlyIdempotent

An anonymous Trailhead Supply cart as it stands: each product with its units and line total, the subtotal, how delivery is charged, when the cart expires, and cart_url, which opens the store's website with the products in the shopper's own cart.

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_token": "<cart_token>"
    },
    "name": "cart_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoAnswer language: en (default en). Names, labels and URLs follow it.
cart_tokenYesThe cart_token an earlier cart answer returned.

Output Schema

NameRequiredDescriptionDefault
linesYes
totalNoWhat the cart costs before delivery, discounts taken off; the store's website shows the same.
limitsYes
cart_urlYesOpens the store's website with these products in the shopper's own cart, where they review and order; nothing is ordered before that.
currencyYes
subtotalYesBefore delivery and the bundle saving.
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
cart_tokenYesPass it to the other cart tools. A secret: whoever holds it can change this cart.
expires_atYesISO 8601; every change pushes it back.
item_countYesUnits over all lines.
answer_typeNoWhat this answer is, for rendering.
vat_includedYes
delivery_hintYesHow delivery is charged, in the answer language.
discount_totalNoThe bundle saving; 0 without a whole bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: the cart is anonymous (no account context needed), the answer includes computed totals and delivery charging, and it discloses the cart's expiry behavior — behavior an agent could not infer from the annotations.

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 front-loaded sentence that leads with the resource and then enumerates the fields in a natural reading order. The enumeration is long but each item is informative; nothing is padding, though it could be tightened slightly.

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?

With only two well-documented parameters and an output schema present, the description need not enumerate return fields, yet doing so is useful because it explains what cart_url means — something an output schema name alone would not convey. It leaves no gap that would block a correct call.

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 100%, with cart_token ('the cart_token an earlier cart answer returned') and locale (enum en, controls names/labels/URLs) both documented in the schema. The description adds no parameter-level meaning of its own, so the 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?

The description names a specific resource (an anonymous Trailhead Supply cart) and frames it as a state snapshot ('as it stands'), and the enumerated contents (units, line total, subtotal, delivery charge, expiry, cart_url) make clear this is a read of existing cart state rather than a mutation. It does not explicitly name a sibling it is not, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative among the cart_add_item / cart_update_item / cart_remove_item siblings. The only actionable usage hint is embedded in a field description: cart_url 'opens the store's website with the products in the shopper's own cart', implying it should be handed to the shopper rather than parsed.

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.