Skip to main content
Glama

Link do carrinho

get_checkout_link
Read-only

Gera o link que abre este carrinho no navegador do cliente, no site da Casa do Artesão, onde ele informa os dados, escolhe o frete e paga. Use para entregar a compra ao cliente.

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_checkout_link"
  }
}

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 declare this is a non-destructive read, so the description's job is to add context — and it does, explaining that the output is a URL the customer opens in their own browser and that the rest of the purchase flow (data entry, shipping choice, payment) happens there. It does not say whether the link expires or is single-use, which would be the remaining valuable disclosure.

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?

Two sentences, front-loaded with the action and its result, with no redundant restatement of the title or annotations. Every clause contributes either what is produced or how it is used.

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 link generator with a fully-described single parameter and no output schema, the description covers what the output is and what the customer does with it. Only link lifetime/reuse behavior is left unstated, which is a minor 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?

Schema coverage is 100% and the single parameter session_token is documented as coming from start_session, so the schema carries the full burden. The description adds no parameter-level meaning beyond that, which is the expected baseline for a fully-documented single-parameter tool.

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 uses a specific verb and resource ('Gera o link que abre este carrinho') and explains exactly what the resulting link does — opens the cart on the Casa do Artesão site for the customer to fill in data, pick shipping and pay. That clearly separates it from data-returning siblings like get_cart, though no sibling is named explicitly.

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?

'Use para entregar a compra ao cliente' gives a clear usage context: hand the checkout off to the buyer. There is no statement of when NOT to use it, and no explicit alternative (e.g., get_cart for reading cart contents internally), so the routing guidance is implied rather than spelled out.

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