Skip to main content
Glama

agtmart sandbox store and agent survey

View sandbox cart

get_cart
Read-only

Show cart lines and totals (subtotal, shipping, tax estimate, total).

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the shape of the returned totals (subtotal, shipping, tax estimate, total), but says nothing about behavior for a missing or expired cart_id, nor about the sandbox context named in the title.

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?

One front-loaded sentence with zero filler; the most useful detail (the list of totals returned) is packed into a parenthetical rather than spread across padding.

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 a simple read-only tool with annotations covering safety and no output schema, the description is nearly sufficient — it outlines the return contents. The remaining gap is the unexplained cart_id and the absence of any error/not-found behavior, both minor for this complexity level.

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?

Schema description coverage is 0% and the single required parameter cart_id is never explained in the description. The name is largely self-evident, but the description does not compensate for the missing schema documentation (e.g., where cart_id comes from or what format it takes).

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 cart lines and totals" pairs a specific verb (show/read) with a specific resource (cart) and even enumerates the returned fields (subtotal, shipping, tax, total). It is clearly distinct from mutating siblings like add_to_cart or checkout, though the distinction is left implicit rather than stated.

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 gives no when-to-use guidance, no mention of alternatives, and no precondition such as the cart needing to exist or being in a sandbox. An agent must infer that this is the read counterpart to add_to_cart, which is reasonable but not stated.

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