Conector Juspronto

Minutas a redigir

minutas_a_redigir

Read-only

Lista os pacotes de Minuta Pronta esperando redação (status PRONTA_PARA_REDIGIR), prazo fatal mais próximo primeiro, até 20, em minutas. Cada item já traz o pacote completo (partes, evidenceIds, checklist); use dados_para_peca, ler_paginas e checar_peca. Use no início do prompt "redigir minutas do dia". Esta conexão não grava peças: entregue o texto ao advogado.

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": "minutas_a_redigir"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`minutas`	No
`mensagem`	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"
+    },
+    "mensagem": {
+      "type": "string"
+    },
+    "minutas": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cnjFormatado": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "minutaProntaId": {
+            "type": "string"
+          },
+          "pasta": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "processoId": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful operational context: the tool does not write peças and the draft must be handed to the lawyer. It also discloses ordering and the 20-item cap, though it does not discuss auth or rate limits.

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?

The description is a single front-loaded paragraph with no filler. Every clause adds useful information: status filter, ordering, limit, package contents, follow-on tools, trigger phrase, and non-writing behavior.

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?

Given the output schema and annotations, the description covers enough for correct invocation: what is returned at a high level, the workflow it starts, and the fact that it does not write peças. Nothing essential is missing for an agent deciding and calling this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no input parameters, so the schema itself has nothing to document and the baseline for zero parameters applies. The description adds no parameter details because none are needed.

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 gives a specific verb and resource: it lists Minuta Pronta packages awaiting drafting, filtered by the PRONTA_PARA_REDIGIR status. It also states ordering and a hard limit, so an agent can distinguish it from generic sibling tools like listar_minutas.

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 clearly says to use this at the start of a 'redigir minutas do dia' prompt and points to follow-on tools (dados_para_peca, ler_paginas, checar_peca). It does not explicitly contrast with listar_minutas or state when not to use it, so it falls short of the top score.

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?