Conector Juspronto

Linha do tempo do processo

linha_do_tempo

Read-only

Linha do tempo de UM processo: andamentos, audiências e prazos em ordem cronológica, com filtro desde/ate. Um evento por ato, agrupado antes de paginar, com idsPorFonte (ID, lista de IDs ou null por fonte), tpuCodigo e teor (disponivel, teorEventoId, status). Use para "histórico do processo" ou "o que aconteceu entre X e Y". Eventos com teorDisponivel trazem teorEventoId: leia com detalhe_processo(processoId, teorEventoId). Para outras peças use buscar_autos ou ler_paginas. Peças sem data vêm à parte em pecasSemData, só na primeira página. Devolve total e proximoCursor quando há mais: chame de novo com cursor igual a ele. Cada leitura de andamentos tem teto de 2.000 linhas mais sentinela; ao atingi-lo, truncado é true, totalExato é false e total é apenas o mínimo conhecido. O aviso pede restringir desde/ate. O cursor continua depois do último ato completo entregue. Dias incompletos são adiados; se nem um dia couber, a consulta para com aviso e sem cursor.

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>"
    },
    "name": "linha_do_tempo"
  }
}

Input Schema

Name	Required	Description
`ate`	No	Fim do período, formato AAAA-MM-DD, inclusivo (opcional)
`desde`	No	Início do período, formato AAAA-MM-DD (opcional)
`cursor`	No	proximoCursor da resposta anterior, para a página seguinte (vale por 1 hora; use com os mesmos processoId, desde e ate)
`limite`	No	Máximo de eventos por página (padrão 40; acima de 100 é cortado em 100)
`processoId`	Yes	ID do processo (obtenha via buscar_processos)

Output Schema

Name	Required	Description	Default
`erro`	No
`aviso`	No
`total`	No
`eventos`	No
`frescor`	No
`temMais`	No
`mensagem`	No
`truncado`	No
`totalExato`	No
`pecasSemData`	No
`avisoConteudo`	No
`proximoCursor`	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": {
+    "aviso": {
+      "type": "string"
+    },
+    "avisoConteudo": {
+      "type": "string"
+    },
+    "erro": {
+      "type": "string"
+    },
+    "eventos": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "data": {
+            "type": "string"
+          },
+          "resumo": {
+            "type": "string"
+          },
+          "tipoEvento": {
+            "type": "string"
+          }
+        },
+        "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"
+        }
+      ]
+    },
+    "mensagem": {
+      "type": "string"
+    },
+    "pecasSemData": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "proximoCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "temMais": {
+      "type": "boolean"
+    },
+    "total": {
+      "type": "number"
+    },
+    "totalExato": {
+      "type": "boolean"
+    },
+    "truncado": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "proximoCursor da resposta anterior, para a página seguinte (vale por 1 hora; use com os mesmos processoId, desde e ate)",
+  "type": "string"
+}

changedInput schema / properties / limite / description

Previous value: -"Máximo de eventos (padrão 40; acima de 100 é cortado em 100)"New value: +"Máximo de eventos por página (padrão 40; acima de 100 é cortado em 100)"

First observedOct 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the read-only safety profile, but the description adds substantial behavior beyond that: a 2.000-line cap per read with sentinela, truncado/totalExato flags, total being only a minimum when truncated, cursor semantics (resumes after the last complete act, 1-hour validity), incomplete days being deferred, and pecasSemData appearing only on the first page. This is exactly the operational context an agent needs to avoid misreading results.

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?

Dense but front-loaded: purpose and routing come before pagination mechanics and edge cases. Every clause carries information, though the final sentence about incomplete days is convoluted and would read better as a separate bullet.

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, yet the description still explains the key return fields an agent must act on (idsPorFonte, tpuCodigo, teor/teorEventoId, pecasSemData, total, proximoCursor, truncado). Combined with pagination and truncation rules, nothing an agent needs to call 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. The description goes further by explaining how desde/ate interacts with truncation (the warning asks you to narrow the range) and that cursor must be reused with the same processoId, desde and ate – semantics that the schema only partially conveys. It never mentions limite, which keeps it from a 5.

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 resource and scope: a chronological timeline of ONE process covering andamentos, audiências and prazos. It is immediately distinguishable from sibling tools, which it names explicitly (detalhe_processo, buscar_autos, ler_paginas).

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?

Gives concrete trigger phrases ("histórico do processo", "o que aconteceu entre X e Y") and routes the agent elsewhere for other artifacts: teor detail goes to detalhe_processo(processoId, teorEventoId), other peças to buscar_autos or ler_paginas. Clear when-to-use and when-not-to-use.

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?