Skip to main content
Glama

ler_decisao

Retrieve detailed metadata from a Brazilian court decision on JusBrasil, including relator, court, and publication date, to generate accurate citations for legal documents.

Instructions

Le uma decisao individual do JusBrasil e extrai todos os metadados.

Use APOS `buscar_jurisprudencia` para montar citacoes completas em peticoes.
A busca da ementa curta; use esta tool para pegar os dados formais
(relator, orgao julgador, data de julgamento) da decisao que voce quer citar.

IMPORTANTE - ANTI-ALUCINACAO:
- Se qualquer campo retornar None/vazio (especialmente `ementa`), NUNCA invente
  nem reconstrua o conteudo com base em memoria ou conhecimento geral.
- Campos nulos indicam FALHA DE EXTRACAO ou AUSENCIA REAL no JusBrasil,
  nao sao convite para preencher com texto plausivel.
- Verifique sempre o campo `_parse_warnings` no retorno. Se ele existir, siga
  estritamente suas instrucoes e comunique ao usuario.
- Para uso em peticao, oriente o usuario a conferir o texto oficial
  diretamente no site do tribunal (scon.stj.jus.br, sites dos TJs, etc.).
- JusBrasil eh agregador privado, NAO eh fonte oficial para citacao formal.

Args:
    url: URL da decisao (ex: "https://www.jusbrasil.com.br/jurisprudencia/tj-pi/1629196340").
         Pegue a URL do campo `url` retornado por `buscar_jurisprudencia`.

Returns:
    Dict com:
    - titulo, tribunal, tipo (Apelacao Civel, etc.)
    - numero_cnj (formato 0000000-00.0000.0.00.0000 pronto pra citacao)
    - relator, orgao_julgador, data_julgamento, data_publicacao
    - ementa (texto completo)
    - citacao_abnt: string ja formatada estilo "(TJ-PI - Apelacao Civel: NNN, Relator: ..., ...)"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses that null fields indicate extraction failure or actual absence, warns against inventing content, and instructs to check _parse_warnings. It also clarifies the non-official nature of JusBrasil, which is critical for the tool's usage.

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 description is well-structured with clear sections (purpose, usage, anti-hallucination, args, returns). It is somewhat lengthy but every sentence serves a purpose. Minor redundancy could be trimmed, but overall it is efficiently organized.

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 no output schema and the complexity of the tool (extracting multiple fields, handling failures, anti-hallucination), the description is remarkably complete. It lists all return fields, provides the citation format, and includes critical usage warnings.

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?

The single parameter 'url' is exhaustively described: it provides an example URL, explains where to obtain it (from buscar_jurisprudencia's 'url' field), and clarifies it should be the full URL. With 0% coverage from the schema, the description fully compensates.

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?

The description clearly states it reads an individual decision from JusBrasil and extracts all metadata. It differentiates from siblings by specifying it is used after buscar_jurisprudencia to obtain formal data (relator, orgao julgador, data de julgamento) for citations. The verb 'ler' and resource 'decisao' are precise.

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 states when to use (after buscar_jurisprudencia) and provides context for building citations in petitions. It also includes anti-hallucination instructions and warnings about JusBrasil not being an official source, guiding appropriate usage.

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