mcp-juridico-brasil

Overview Schema Source Related Servers Discussions Admin

executar_monitoramento_em_lote

Monitor up to 50 Brazilian legal processes in a single batch, automatically skipping duplicates and tolerating individual failures. Read-only RPA cycle retrieves case updates without confirming DJe communications.

Instructions

Executa um ciclo RPA finito e tolerante a falhas para ate 50 processos.

Cada alvo deve conter numero_processo, tribunal e desde_iso. Alvos duplicados sao consultados uma unica vez. Falha em um processo nao cancela os demais. A rotina e somente leitura: nunca confirma comunicacao/intimacao no DJe.

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": {
      "alvos": "<alvos>"
    },
    "name": "executar_monitoramento_em_lote"
  }
}

Input Schema

Name	Required	Description	Default
`alvos`	Yes
`concorrencia`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 31, 2026

TDQS

A4/5.0

Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure and does so well: it says the run is finite, fault-tolerant, deduplicated, failures do not cancel other processes, and—critically—it is read-only and never confirms notifications in DJe. This gives the agent a clear safety model.

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?

Five short sentences, each carrying distinct information: scope, required target fields, dedup, fault tolerance, and side-effect safety. The purpose is front-loaded and every sentence earns its place.

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 no-annotation tool with a non-trivial RPA behavior, the description covers input requirements, failure semantics, and side-effect safety; the output schema handles return values. The only notable gap is the undocumented 'concorrencia' parameter, and the description does not say what happens when more than 50 targets are supplied.

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 0%, so the description must compensate. It documents the required shape of each 'alvos' entry (numero_processo, tribunal, desde_iso) and deduplication behavior, but it says nothing about the 'concorrencia' parameter, leaving its semantics to inference from its name and default value.

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 first sentence states a concrete action and scope: executes a finite, fault-tolerant RPA cycle for up to 50 processes. This clearly identifies the batch-monitoring function, but it does not name or contrast any sibling such as monitorar_processo, so differentiation is left to the reader.

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 description signals batch context (até 50 processos) and implies this is for multiple targets, but it never states when to choose this tool over singular tools like monitorar_processo or listar_movimentacoes. There are no explicit when/not-when conditions or alternative routing.

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