Conector Juspronto

Carteira do escritório

carteira

Read-only

Mostra indicadores da carteira compartilhada, agrupados por situação da pasta, advogado ou tribunal, prazos abertos da semana civil de segunda a domingo em Brasília e processos sem movimento há mais de 30 dias. diasSemMovimento muda o indicador e filtra a lista; sem movimento registrado, conta desde a criação da pasta. Inclui a contagem e os nomes dos advogados com OAB fora da varredura. A lista tem 25 itens por página; use proximoCursor com os mesmos filtros para continuar. truncado e aviso indicam corte por tamanho. Para localizar um caso, prefira 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": "carteira"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	proximoCursor da página anterior, com os mesmos filtros
`agruparPor`	No	Agrupamento dos indicadores, padrão situacao
`diasSemMovimento`	No	Filtra a lista por mais de N dias sem movimento; o indicador usa 30 dias quando omitido

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

addedOutput schema / properties / oabNaoConsta

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

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"
+    },
+    "indicadores": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "itens": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cnjFormatado": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "pasta": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "processoId": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "oabsForaDaVarredura": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "proximoCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncado": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: it discloses the 25-item page size, the cursor continuation rule, the meaning of truncado/aviso as size-cut signals, the default 30-day indicator window, and the edge case that a folder with no recorded movement counts from its creation date. It even defines the week as Monday–Sunday in Brasília time, which materially affects the prazos indicator.

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 the core purpose and organized by concern (indicators, diasSemMovimento semantics, OAB caveat, pagination, truncation, alternative tool). Dense but every sentence carries information; only the truncado/aviso sentence is slightly terse relative to its importance.

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?

An output schema exists, so return values need not be described, and the description still covers pagination, truncation flags, default windows, and the OAB out-of-scan caveat. Nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: diasSemMovimento both switches the indicator and filters the list, and when omitted the indicator falls back to 30 days. That dual effect is not derivable from the schema alone. The agruparPor parameter gets no extra treatment beyond what the enum already conveys.

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 and resource ("Mostra indicadores da carteira compartilhada") and immediately enumerates the grouping dimensions (situação da pasta, advogado, tribunal) plus the scope of the indicators (prazos da semana civil, processos sem movimento há mais de 30 dias). It also names a sibling, buscar_processos, as the tool for locating a single case, so an agent can distinguish the two without opening either 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?

Gives an explicit routing rule for the main confusion case ("Para localizar um caso, prefira buscar_processos") and explains how to continue paging with the same filters. It stops short of stating when this tool should NOT be used at all (e.g., per-client financial views), but the intended context is clear.

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?