Skip to main content
Glama

Abrir sessão de compra

start_session

Abre uma sessão de compra com um carrinho vazio e devolve o session_token. Guarde o token e passe-o em todas as ferramentas de carrinho. A sessão expira 7 dias após o último uso.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_nameNoNome do assistente ou app (ex.: "ChatGPT", "Claude"), para estatística.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds genuinely new behavior: the return value (session_token) and a 7-day idle expiry, which affects whether the agent must re-open a session. It does not cover failure modes or whether re-calling creates a duplicate session, keeping it below a 5.

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?

Three short sentences: what it does, what to do with the token, and the expiry constraint — front-loaded with zero filler. Every sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the returned token and its lifetime, and with one optional parameter the schema covers inputs fully. Nothing an agent needs in order to call this correctly and use the result is missing.

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 optional parameter client_name is fully documented in the schema, so the baseline is 3. The description adds nothing about the parameter (nor needs to), and its value-add is about the token rather than inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("abre uma sessão de compra") plus the concrete result ("carrinho vazio" and "devolve o session_token"). No sibling tool creates sessions, so an agent can identify this as the entry point of the purchase flow without inspecting schemas.

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

Usage Guidelines4/5

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

"Guarde o token e passe-o em todas as ferramentas de carrinho" makes the downstream usage pattern explicit and establishes this as the prerequisite step for the cart tools. It stops short of stating when-not to use it (e.g., reuse an existing token instead of starting a new session), so it is clear context rather than full when/when-not guidance.

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