Conector Juspronto

Processos do Diário fora do cadastro

processos_no_diario

Read-only

Lista CNJs válidos com publicações locais para a OAB do escritório e sem pasta, em páginas de 25 com total, proximoCursor e truncado. Exclui os processos marcados pelo advogado como fora do escritório. Cada item informa cnjFormatado, tribunal, publicacoes e ultimaEm. Use proximoCursor para continuar a consulta. Esta conexão só consulta os dados locais. Para a carteira cadastrada, prefira carteira ou buscar_processos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "processos_no_diario"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	proximoCursor da página anterior da lista

Output Schema

Name	Required	Description	Default
`aviso`	No
`itens`	No
`total`	No
`truncado`	No
`avisoConteudo`	No
`proximoCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026

removedInput schema / properties / confirmacaoToken

Removed value: -{
-  "description": "Token da prévia, após o advogado confirmar; repetir os mesmos argumentos",
-  "type": "string"
-}

removedInput schema / properties / importar

Removed value: -{
-  "description": "Até 25 CNJs encontrados no Diário local; sem token devolve prévia, com token confirma o cadastro das pastas",
-  "items": {
-    "maxLength": 64,
-    "minLength": 1,
-    "type": "string"
-  },
-  "maxItems": 25,
-  "minItems": 1,
-  "type": "array"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "aviso": {
+      "type": "string"
+    },
+    "avisoConteudo": {
+      "type": "string"
+    },
+    "itens": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cnjFormatado": {
+            "type": "string"
+          },
+          "publicacoes": {
+            "type": "number"
+          },
+          "ultimaEm": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "proximoCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncado": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedNov 5, 2026

addedInput schema / properties / confirmacaoToken

Added value: +{
+  "description": "Token da prévia, após o advogado confirmar; repetir os mesmos argumentos",
+  "type": "string"
+}

addedInput schema / properties / importar

Added value: +{
+  "description": "Até 25 CNJs encontrados no Diário local; sem token devolve prévia, com token confirma o cadastro das pastas",
+  "items": {
+    "maxLength": 64,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 25,
+  "minItems": 1,
+  "type": "array"
+}

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": {},
-  "properties": {
-    "aviso": {
-      "type": "string"
-    },
-    "avisoConteudo": {
-      "type": "string"
-    },
-    "itens": {
-      "items": {
-        "additionalProperties": {},
-        "properties": {
-          "cnjFormatado": {
-            "type": "string"
-          },
-          "publicacoes": {
-            "type": "number"
-          },
-          "ultimaEm": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "proximoCursor": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "total": {
-      "type": "number"
-    },
-    "truncado": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedOct 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "aviso": {
+      "type": "string"
+    },
+    "avisoConteudo": {
+      "type": "string"
+    },
+    "itens": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cnjFormatado": {
+            "type": "string"
+          },
+          "publicacoes": {
+            "type": "number"
+          },
+          "ultimaEm": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "proximoCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncado": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

AddedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description only needs to add context, which it does: page size of 25, presence of total, proximoCursor and truncado, the exclusion rule, and the note that this connection reads only local data. Return-format details are somewhat redundant given the output schema, keeping it at 4.

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-loaded with scope and exclusions, then pagination mechanics, then sibling routing — a sensible order. Slight redundancy in mentioning proximoCursor both in the return-fields list and in the continuation sentence, but every clause carries 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 a one-parameter, read-only list tool with annotations and an output schema, the description supplies everything an agent needs: what qualifies for inclusion, what is excluded, page size, pagination continuation, and where to go instead for the registered portfolio.

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?

Only one optional parameter with 100% schema description coverage, so the schema already carries the semantics. The description repeats its purpose ('Use proximoCursor para continuar a consulta') but adds no syntax, format, or edge-case guidance beyond the schema.

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 (lista) and a precisely scoped resource: CNJs with local publications for the office's OAB and without a folder. The exclusion rule (processes the lawyer marked as outside the office) and the explicit contrast with carteira/buscar_processos let an agent distinguish it from siblings without opening the schema.

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?

The final sentence routes the agent explicitly to carteira or buscar_processos when the registered portfolio is what's wanted, and 'Use proximoCursor para continuar a consulta' gives the follow-up procedure. There is no explicit statement of when not to use it beyond the alternative suggestion, so it stops short of a full 5.

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?