Conector Juspronto

Abrir resultado

fetch

Read-only

Recupera o conteúdo completo de um ID retornado por search: processo: devolve a ficha do processo; pagina: devolve o teor da página dos autos.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	ID opaco vindo de search (processo:<id> ou pagina:<evidenceId>)

Output Schema

Name	Required	Description
`id`	Yes	O mesmo ID recebido
`url`	Yes	Link para abrir o documento no JusPronto (fonte da citação)
`text`	Yes	Conteúdo: a ficha do processo ou o teor da página (até 40 mil caracteres)
`title`	Yes	Título legível do documento
`metadata`	Yes	Dados de apoio; metadata.tipo é processo, pagina ou nao_encontrado

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds useful behavioral distinction between the two ID prefixes (processo returns the ficha, pagina returns the page content), which is genuine information beyond the annotations, but it doesn't discuss rate limits, size, or errors.

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?

A single compact sentence front-loads the purpose and then enumerates the two ID types. Every clause earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with an output schema present and annotations covering safety, the description supplies the key routing semantics (which ID prefix yields which result). It doesn't cover edge cases like invalid IDs, but the essential call contract is complete.

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% and the schema already describes 'id' as an opaque value from search. The description adds meaningful semantics by explaining the two prefix forms and what each returns, going beyond the generic schema note, though it doesn't add format details the schema lacks.

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 (recupera) and resource (conteúdo completo de um ID), and explicitly explains the two ID forms returned by search: processo:<id> and pagina:<evidenceId>. This differentiates it from siblings like search and detalhe_processo by scoping it to fetching content for IDs already produced by search.

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?

Clearly implies usage: retrieve full content of an ID returned by search, with distinct behavior per ID prefix. It doesn't explicitly state when NOT to use it or name alternatives like detalhe_processo or ler_paginas, but the search-produced-ID precondition is a strong usage cue.

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?