Skip to main content
Glama

ler_inteiro_teor

Retrieves the complete text of a Brazilian court decision, including report, votes, and full judgment, from a JusBrasil URL. Requires authentication.

Instructions

Extrai o TEXTO INTEGRAL de uma decisao (relatorio + voto + acordao completos).

Diferente de `ler_decisao` (que traz so metadados + ementa), esta tool retorna
o inteiro teor do julgado. EXIGE login (credenciais configuradas no Keychain);
sem sessao autenticada o conteudo nao vem.

IMPORTANTE - ANTI-ALUCINACAO:
- Se `texto` voltar nulo/vazio, NUNCA invente o conteudo do acordao. Significa
  que o inteiro teor nao esta disponivel no JusBrasil para esta decisao, ou que
  a sessao nao esta autenticada. Informe o usuario e oriente a consultar o
  inteiro teor no site oficial do tribunal.
- Verifique `_parse_warnings` no retorno e siga suas instrucoes.
- JusBrasil eh agregador privado, NAO eh fonte oficial para citacao formal.

Args:
    url: URL da decisao (ex.: ".../jurisprudencia/tj-pi/1629196340") OU a URL
         direta de inteiro teor (".../inteiro-teor-NNN").

Returns:
    Dict com url, url_inteiro_teor, texto (texto integral), n_caracteres,
    autenticado (bool).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
Behavior5/5

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

Describes login requirement, behavior when no session, anti-hallucination instructions, limitations of JusBrasil, and return format. No annotations present so description carries full burden and does it thoroughly.

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?

Well-structured with clear sections, but slightly verbose with repeated emphasis on anti-hallucination. Every sentence is valuable, though could be tightened.

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?

Covers all important aspects: purpose, usage distinction, authentication, error handling, return format, and source reliability. No output schema, but description explains return dict fields fully.

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

Parameters5/5

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

Schema provides no description for url, but the tool's Args section explains that url can be a decision URL or a direct full-text URL with example. This adds essential meaning beyond the schema.

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?

Description clearly states it extracts full text of a decision (report, vote, full judgment) and distinguishes from sibling ler_decisao which only returns metadata and summary.

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?

Explicitly contrasts with ler_decisao, provides authentication requirement, anti-hallucination guidance on null texto, and warns that JusBrasil is not official source.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fxbarros/mcp-jusbrasil'

If you have feedback or need assistance with the MCP directory API, please join our Discord server