Skip to main content
Glama

Buscar logs de acesso

buscar_logs_acesso
Read-only

Retrieves buyer access logs for a digital product membership area—timestamps, email, masked IP, and lesson—to support chargeback disputes where the purchase is not recognized.

Instructions

Só para produto digital: acessos do comprador à área de membros (data/hora, e-mail, IP parcialmente mascarado, aula). É a principal prova em 'não reconheço a compra' (Cláusula 8.5.D).

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

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

A3.8/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, so the description only needs to add context beyond that. It does add useful traits: the IP is partially masked (so the agent should not promise a full IP), and the log is framed as the primary evidence under Clause 8.5.D, which tells the agent how to weigh it. It says nothing about behavior when the contestação is not a digital product or about volume/pagination.

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 short sentences, front-loaded with the gating condition ('Só para produto digital') before the payload and the legal use case. Every clause carries information: scope, return fields, and evidentiary purpose. No filler.

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 one-parameter, read-only lookup with no output schema, the description covers scope, returned fields and purpose, which is enough to call it correctly. The remaining gaps (empty-result behavior, whether non-digital products error out) are minor but real, so it is not a 5.

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 contestacao_id parameter is fully documented with a pattern (^CB-\d{3,}$) and an example (CB-002). The description adds nothing about the parameter, so the baseline 3 applies since the schema already carries the meaning.

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 names a specific verb and resource (buyer access logs to the members area) and pins the scope with 'Só para produto digital', which separates it from the order, tracking, conversation and document siblings. It also enumerates the returned fields (date/time, e-mail, masked IP, lesson), so an agent knows exactly what data it gets. It stops short of explicitly routing to a named alternative, which keeps it at 4 rather than 5.

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 gives a clear positive condition ('Só para produto digital') and a concrete scenario where it matters most ('não reconheço a compra'). That is real when-to-use guidance rather than an implied purpose. It does not say what to use when the product is not digital, so it lacks the exclusion/alternative half of a 5.

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