Conector Juspronto

Contexto atual do processo

montar_contexto

Read-only

Monta evidências locais para uma pergunta, sem gerar texto nem consultar fornecedores: ficha com fonte e frescor, prazos abertos e sugestões pendentes, andamentos e intimações desde o dia do último download dos autos em Brasília e trechos encontrados pela pergunta, sem páginas repetidas. Cada parte informa dataDeCorte. limiteTokens aceita inteiro de 1000 a 20000, padrão 8000, estimado em 4 caracteres por token, incluindo o JSON final após a máscara do perfil. O corte preserva essa ordem de prioridade: os trechos saem primeiro. truncado e aviso informam o que ficou de fora. Use para reunir o estado atual antes de responder; para ler uma evidência inteira, prefira ler_paginas. Processo sigiloso continua marcado e só são lidos dados do escritório. LIMITE_CONTEXTO_INVALIDO pede corrigir o limite.

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

Input Schema

Name	Required	Description
`pergunta`	Yes	Pergunta usada para localizar os trechos relevantes dos autos
`processoId`	Yes	ID do processo obtido em buscar_processos
`limiteTokens`	No	De 1000 a 20000 tokens estimados; padrão 8000, com 4 caracteres por token

Output Schema

Name	Required	Description	Default
`aviso`	No
`pasta`	No
`partes`	No
`truncado`	No
`processoId`	No
`cnjFormatado`	No
`limiteTokens`	No
`avisoConteudo`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses truncation behavior ('truncado e aviso informam o que ficou de fora'), cut priority order, token accounting details, confidential-process marking, office-only data scope, and the LIMITE_CONTEXTO_INVALIDO error condition. These are exactly the operational traits an agent needs before calling.

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?

The purpose is front-loaded and every sentence carries operational information. The text is dense and packs multiple concepts into long clauses, which slightly hurts readability, but there is little outright redundancy beyond repeating the token range already in the schema.

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 an output schema, the description need not explain return values, yet it helpfully names the assembled sections and truncation indicators. Annotations cover safety; the description covers scope, limits, error handling, and alternatives. Nothing material is missing for correct invocation.

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 schema already documents the three parameters. The description adds value by explaining token estimation (4 characters per token) and that the final JSON after profile masking counts toward the limit, plus the priority order used when cutting. It does not add much about 'processoId' beyond the schema's reference to buscar_processos, but overall it exceeds baseline.

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 ('monta evidências locais para uma pergunta') and enumerates the contents assembled: ficha com fonte/frescor, prazos, sugestões, andamentos, intimações e trechos. It also explicitly excludes text generation and supplier calls, making the scope unambiguous.

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 an explicit use case ('Use para reunir o estado atual antes de responder') and names the alternative for a different need ('para ler uma evidência inteira, prefira ler_paginas'). This is a clear when-to-use/when-to-use-something-else instruction.

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?