Skip to main content
Glama

Listar contestações abertas

listar_contestacoes
Read-only

Lists a producer's open chargebacks ordered by nearest deadline, helping identify which case is most urgent within the 48-hour evidence window.

Instructions

Lista as contestações (chargebacks) abertas do produtor, ordenadas pelo menor prazo. O prazo para enviar provas é de 2 dias corridos (48h) a partir da abertura (Cláusula 8.9). Use para responder qual contestação é a mais urgente. Mencione a urgência ao listar; nas respostas seguintes não repita lembretes de urgência a cada mensagem.

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": "listar_contestacoes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds behavior the annotations do not: the list covers only OPEN chargebacks, it is sorted by shortest deadline, and the proof-submission window is 2 calendar days (48h) from opening under Cláusula 8.9. What it omits is the shape of each returned item, which matters somewhat since there is no output schema.

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?

The scope and the 48h rule are front-loaded in the first two sentences, which is the right order for an agent deciding whether to call. The closing instruction about repeating urgency reminders is slightly meta and could read as prompt style rather than tool documentation, but it is short and does affect how results are presented.

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 zero-parameter, read-only listing tool with no output schema, the description covers what is listed, how it is ordered, and the deadline that drives urgency. It leaves the returned fields per chargeback unstated, which is the main remaining gap given the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the parameter-semantics baseline is 4. There is no input for the description to explain, and it does not confuse the reader with input-like details.

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 gives a specific verb and resource ("Lista as contestações (chargebacks) abertas do produtor") plus the scoping qualifiers 'abertas' and 'do produtor'. It also states the ordering, so an agent can distinguish this listing tool from the search/consult siblings without opening the schema.

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?

It states the concrete use case clearly: "Use para responder qual contestação é a mais urgente". That is a real when-to-use condition rather than an implied one. It stops short of naming an alternative sibling or stating when not to use it, so it is clear context without explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.