Skip to main content
Glama

Ver carrinho

get_cart
Read-only

Mostra o carrinho: itens, subtotal, desconto do cupom, frete, total em reais, se já pode ser finalizado e o que falta (erros).

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

Input Schema

NameRequiredDescriptionDefault
session_tokenYesO session_token devolvido por start_session.

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 establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description's burden is reduced. It still adds real context beyond them: the response includes checkout eligibility and the specific errors/remaining gaps that block checkout, which is exactly what an agent needs to decide the next step. It does not mention currency handling beyond "em reais" or staleness of the cart.

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?

A single dense sentence front-loaded with the resource and followed by the returned fields in logical order (itens → valores → frete → total → status). Zero filler, nothing redundant with the title beyond the resource name.

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?

Read-only, single-parameter, no output schema – so describing the return payload in the description is the right call and it does so. A brief note on when the cart may be empty or invalid (e.g. expired session_token) would close the remaining gap.

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?

Only one parameter (session_token) and schema description coverage is 100%, with the schema itself stating it comes from start_session. The description adds no meaning about the parameter or its failure modes, so the baseline 3 for schema-does-the-work 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+resource ("Mostra o carrinho") and enumerates exactly what is returned: items, subtotal, coupon discount, shipping, total in BRL, checkout readiness and blocking errors. It is clearly a read operation against the same cart the sibling mutation tools act on, though it never names an alternative. Missing only explicit sibling differentiation.

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?

Usage is only implied by the verb "Mostra" and the readOnly annotation – an agent can infer this is the way to inspect the cart before calling place_order, but the description never says when to call it or when to prefer another tool. No prerequisites or exclusions are 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