Skip to main content
Glama

Confirmar Leitura Intimacao

confirmar_leitura_intimacao

Confirms reading of an electronic court intimation, records official awareness, and starts the procedural deadline; defaults to a safe simulation unless confirmation is enabled.

Instructions

Confirma a leitura de uma intimação no Domicílio Judicial Eletrônico.

╔══════════════════════════════════════════════════════════════════╗ ║ AÇÃO DE ALTO RISCO - EFEITO JURÍDICO REAL E IRREVERSÍVEL ║ ║ ║ ║ Confirmar a leitura de uma intimação via API DJe: ║ ║ - Registra ciência oficial com timestamp no sistema do CNJ. ║ ║ - INICIA a contagem do prazo processual correspondente. ║ ║ - NÃO pode ser desfeito via API. ║ ╚══════════════════════════════════════════════════════════════════╝

GATE DE SEGURANÇA (duplo): Esta tool opera em modo dry-run (sem efeito) por padrão. Para executar com efeito jurídico real, ambas as condições abaixo devem ser satisfeitas:

  1. confirmar=True deve ser passado explicitamente nesta chamada.

  2. DJE_PERMITIR_CONFIRMACAO_LEITURA=true deve estar definida no ambiente.

Se qualquer uma das condições falhar, a tool retorna uma simulação sem qualquer chamada à API DJe - completamente seguro.

Credenciais necessárias (via variáveis de ambiente): DJE_CLIENT_ID - client_id OAuth2 DJE_CLIENT_SECRET - client_secret OAuth2 DJE_BEHALF_OF_CPF - CPF do responsável (auditoria) DJE_PERMITIR_CONFIRMACAO_LEITURA - deve ser 'true' para modo real

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": {
      "numero_processo": "<numero_processo>",
      "id_intimacao": "<id_intimacao>"
    },
    "name": "confirmar_leitura_intimacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmarNoDEVE ser True para indicar que o operador está ciente do efeito jurídico e deseja prosseguir. False por padrão. Mesmo com True, a operação só é executada se DJE_PERMITIR_CONFIRMACAO_LEITURA=true estiver no ambiente.
id_intimacaoYesID único da intimação no DJe (obtido via listar_intimacoes).
numero_processoYesNúmero CNJ do processo (ex: '0001234-56.2023.8.26.0100').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and delivers: it discloses that the action registers official ciência with a CNJ timestamp, STARTS the procedural deadline clock, and cannot be undone via API. It further documents the dry-run default and the two-condition safety gate plus required OAuth credentials, which is exactly the behavioral detail an agent needs before invoking an irreversible operation.

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?

Content is front-loaded with purpose, then risk, then gate conditions, then credentials, which is the right order for a dangerous write. The boxed ASCII banner consumes significant vertical space for three bullet points, which is heavier formatting than necessary, though each line still carries distinct, decision-relevant 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?

For an irreversible, credential-gated mutation the description covers effect, reversibility, gating, defaults and required environment variables; an output schema exists so return-value detail is correctly omitted. Nothing an agent needs to avoid an accidental legal filing is absent.

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 description coverage is 100%, so the baseline is 3 and the schema already explains confirmar, id_intimacao and numero_processo in detail. The description reinforces the confirmar gate and adds credential/audit context (DJE_BEHALF_OF_CPF), but adds no new per-parameter format or semantics beyond what the schema properties state.

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 opens with a specific verb+resource: 'Confirma a leitura de uma intimação no Domicílio Judicial Eletrônico', which is unmistakably distinct from sibling listing tools like listar_intimacoes and buscar_comunicacoes_djen. An agent knows exactly what action is being taken and against which system.

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 precisely when the call has real effect (confirmar=True plus DJE_PERMITIR_CONFIRMACAO_LEITURA=true) and that otherwise it returns a safe simulation, which is strong conditional guidance. It also points to listar_intimacoes as the source of id_intimacao. What is missing is explicit when-not-to-use advice, e.g. verifying the intimação is the intended one before confirming.

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