Skip to main content
Glama

Buscar conversas

buscar_conversas
Read-only

Retrieve buyer-producer messages by contestação ID to gather complementary chargeback evidence and support Clause 8.5.E.

Instructions

Mensagens trocadas entre produtor e comprador (autor, data, texto). Servem como prova complementar (Cláusula 8.5.E).

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": {
      "contestacao_id": "<contestacao_id>"
    },
    "name": "buscar_conversas"
  }
}

Input Schema

NameRequiredDescriptionDefault
contestacao_idYesID da contestação, ex.: CB-002

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the data are complementary evidence under a specific clause, which is useful domain context, but it says nothing about ordering, whether all conversations for the contestação are returned, or what an empty result means.

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?

Two short sentences with no padding, and the resource definition is front-loaded before the evidentiary caveat. Minor inefficiency: the parenthetical field list and the clause citation are cryptic without knowing the surrounding contract, but nothing is wasted.

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

Completeness3/5

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

For a read-only lookup with a single fully documented parameter and no output schema, the description covers what the data are and why they matter. It is still missing the essential operational facts: that it operates per contestação ID and what the caller receives when no conversations exist.

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%: contestacao_id is documented with a pattern and an example (CB-002), so the schema does the heavy lifting. The description never mentions the parameter or clarifies whether it scopes to a single contestação's message thread, so it adds no meaning beyond the schema — baseline 3.

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

Purpose3/5

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

The description identifies the resource ("Mensagens trocadas entre produtor e comprador") and even lists the fields returned (autor, data, texto), which distinguishes it from siblings like buscar_documentos or buscar_logs_acesso. However, it never states the operation: it is not clear whether this searches, lists, or fetches all messages for a given contestação, nor what scope the single ID controls.

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?

The clause "Servem como prova complementar (Cláusula 8.5.E)" implies a usage context — evidence gathering within a contestation — which is a genuine when-to-use hint. But no alternative is named (e.g., versus buscar_documentos or conferir_provas) and there is no statement of when this tool should not be used.

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