Conector Juspronto

Analisar processo

analisar_processo

Read-only

Responde a uma pergunta sobre um processo lendo os autos no servidor (o texto inteiro quando cabe; senão, os trechos mais relevantes) e devolve a resposta com cada citação conferida contra a página, as páginas usadas (evidencias, com citação e link para o documento), as afirmações por classe (afirmacoes) e até quando vão os autos e os andamentos (frescor). Se houver ato decisório depois dos autos baixados, o texto da resposta começa avisando. Erros possíveis: SEM_EVIDENCIA (sem texto nos autos para a pergunta, sem gastar orçamento: use buscar_autos ou ler_paginas), ANALISE_PENDENTE, ANALISE_VAZIA, ANALISE_INDISPONIVEL, ANALISE_RECUSADA e ORCAMENTO_ESGOTADO (diz quando volta). Com frescor null, atos posteriores aos autos não foram verificados. Passando de 20 mil tokens, evidencias, afirmacoes e citacoes saem cortadas do fim, com avisoTamanho. Não altera dados, mas é a mais lenta e consome a cota de análise do escritório: use depois de processo_status e, para fato pontual, prefira buscar_autos ou ler_paginas.

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": {
      "processoId": "<processoId>",
      "pergunta": "<pergunta>"
    },
    "name": "analisar_processo"
  }
}

Input Schema

Name	Required	Description
`modo`	No	fast = só os trechos mais relevantes (mais rápido); deep = os autos inteiros quando cabem (padrão)
`pergunta`	Yes	Pergunta a ser analisada
`processoId`	Yes	ID do processo

Output Schema

Name	Required	Description	Default
`status`	No
`analise`	No
`frescor`	No
`citacoes`	No
`afirmacoes`	No
`evidencias`	No
`avisoTamanho`	No
`avisoConteudo`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "afirmacoes": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "analise": {
+      "type": "string"
+    },
+    "avisoConteudo": {
+      "type": "string"
+    },
+    "avisoTamanho": {
+      "type": "string"
+    },
+    "citacoes": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "evidencias": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "frescor": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "andamentosAte": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "atosDepoisDosAutos": {
+              "items": {
+                "additionalProperties": {},
+                "properties": {
+                  "andamentoId": {
+                    "type": "string"
+                  },
+                  "data": {
+                    "type": "string"
+                  },
+                  "descricao": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "autosAte": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "aviso": {
+              "type": "string"
+            },
+            "djenAte": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "truncado": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare read-only/non-destructive, but the description discloses the expensive traits an agent actually needs: it is the slowest tool, it consumes the firm's analysis quota, results are truncated past 20k tokens with avisoTamanho, and a null frescor means later filings were not checked. It also enumerates the concrete failure codes (SEM_EVIDENCIA, ANALISE_PENDENTE, ORCAMENTO_ESGOTADO with recovery time), which is behavior no structured field carries.

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?

Front-loads what the tool does and its return shape, then moves to errors, limits and alternatives — every sentence carries information. It is dense and packs the five error codes into one run-on sequence, which costs some scannability, but nothing is filler.

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 a quota-consuming, slow, read-only analysis call with an output schema, the description covers what an agent must know: cost, latency, truncation, freshness semantics and full error taxonomy. Nothing needed to decide whether and how to call it is missing.

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 both required parameters plus the fast/deep enum are already documented in the schema. The phrase 'o texto inteiro quando cabe; senão, os trechos mais relevantes' adds operational meaning to the modo choice, but that is the extent of it — baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource: answers a question ('pergunta') about a case file ('processo') by reading the autos and returning the answer with page-verified citations. The scope is precise enough to distinguish it from resumo_processo, detalhe_processo and buscar_autos without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternatives explicitly and the conditions that select them: use after processo_status, and for a point fact prefer buscar_autos or ler_paginas. It also names buscar_autos/ler_paginas as the recovery path on the SEM_EVIDENCIA error, so the routing is complete in both directions.

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

All Conector Juspronto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?