Conector Juspronto

Conferir citação

resolver_citacao

Read-only

Resolve um evidenceId (processo://...) e devolve o texto completo da página com a citação pronta, como (ID 100000001, p. 2) com o ID do documento no PJe e a página dele, ou (p. 37 do PDF) quando os autos não têm o rodapé do PJe, além do tipo do documento, da data e o link, que abre o processo no JusPronto com o documento destacado e o botão para abrir o PDF na página citada. Use quando precisar conferir uma citação.

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": {
      "evidenceId": "<evidenceId>"
    },
    "name": "resolver_citacao"
  }
}

Input Schema

Name	Required	Description	Default
`evidenceId`	Yes	Identificador evidenceId (ex: processo://.../pagina/...)

Output Schema

Name	Required	Description	Default
`url`	No
`pagina`	No
`frescor`	No
`encontrada`	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": {
+    "avisoConteudo": {
+      "type": "string"
+    },
+    "encontrada": {
+      "type": "boolean"
+    },
+    "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"
+        }
+      ]
+    },
+    "pagina": {
+      "additionalProperties": {},
+      "properties": {
+        "evidenceId": {
+          "type": "string"
+        },
+        "paginaLocal": {
+          "type": "number"
+        },
+        "pecaId": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "texto": {
+          "type": "string"
+        },
+        "tituloDaPeca": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral detail beyond them: it returns the whole page text, formats the citation differently depending on whether the PJe footer exists ('ID..., p. 2' vs 'p. 37 do PDF'), and includes document type, date and a deep link. That fallback logic is the kind of context annotations cannot express.

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?

One sentence that is dense but front-loaded with the verb and the outcome, closing with the usage cue. Despite describing several return components, every clause carries information an agent cannot get from the name alone, and the output-schema overlap is minor.

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?

With one required parameter, full schema coverage, an output schema and readOnly annotations, the description covers what the tool does and what comes back well enough to call it correctly. What is missing is only sibling routing, which fits better under usage guidelines.

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 evidenceId parameter is already documented with a processo://... example, so the baseline of 3 applies. The description restates the format but adds no new syntax or constraint information about the identifier.

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?

States a specific verb and resource: resolves an evidenceId (processo://...) and returns the full page text plus a ready-made citation string. It does not, however, distinguish itself from plausible siblings such as ler_paginas or fetch, which an agent would need to disambiguate.

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 closing line 'Use quando precisar conferir uma citação' gives an implied usage context, but it names no alternatives and no when-not conditions. With siblings like ler_paginas, buscar_autos and fetch in the toolset, the agent must infer which one to pick.

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?