Skip to main content
Glama

Elden — Jurisprudência e Legislação Brasileira (MCP)

pesquisa_juridica

Read-only

PESQUISA JURÍDICA, EM UMA CHAMADA (somente leitura; comece por aqui; se for tese complexa ou nova, chame contexto_ler(o_que="inicio") para ver o guia e estilos). Escreva a pergunta como o advogado faria e a ferramenta identifica o que é: uma TESE ("dano moral por extravio de bagagem") devolve súmulas/temas, os acórdãos mais próximos (ementa, órgão, link do tribunal) e artigos pertinentes; um ARTIGO ("art. 14 do CDC") devolve o texto exato, com vigência registrada e link oficial; uma SÚMULA ou TEMA ("Súmula 479 do STJ") confere e mostra o enunciado; um NÚMERO de processo (CNJ, "REsp 2188655") confere que existe e mostra ementa, órgão e link. Passe SEMPRE tribunal_da_causa (sigla, ex.: TJCE): o julgado local sobe sem excluir os demais; tribunal restringe a busca a um tribunal; diploma (sigla) restringe a lei. Para ler o VOTO, chame com abrir_inteiro_teor="<número CNJ>" (planos pagos; texto longo vem em partes: continue com inicio, e publicacao quando a resposta indicar). Isto localiza fontes, não aprova tese: leia antes de citar e transcreva só texto efetivamente lido.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pesquisa_juridica"
  }
}

Input Schema

NameRequiredDescriptionDefault
inicioNo
diplomaNo
perguntaNo
tribunalNo
publicacaoNo
tribunal_da_causaNo
abrir_inteiro_teorNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces read-only while adding non-obvious behavior: full-text reading requires paid plans, long text arrives in parts requiring continuation via `inicio`/`publicacao`, and results are source-locating rather than thesis-approving. The only gap is that it does not describe result volume or rate limits.

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?

Front-loaded with the one-call promise and the entry-point hint, then organized by query type, then by parameter. It is dense and long for a single paragraph, but nearly every clause carries operational information; minor tightening of the return-type enumeration would help.

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?

For a 7-parameter, zero-schema-documentation tool with an output schema, the description covers input semantics, the paid-plan and pagination caveats, and the citation-safety caveat. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 0% across 7 parameters, so the description carries the full burden and does: it explains pergunta (natural-language question), tribunal_da_causa (sigla, e.g. TJCE, and that local rulings do not exclude others), tribunal (restricts search), diploma (restricts to a statute), abrir_inteiro_teor (CNJ number), plus inicio and publicacao as continuation cursors. Every parameter gains meaning beyond its bare name.

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 ('PESQUISA JURÍDICA, EM UMA CHAMADA') and then enumerates the four query shapes it accepts (tese, artigo, súmula/tema, número de processo) with what each returns. It also names the sibling contexto_ler for the case it does not cover, so an agent can separate it from alternatives without opening a schema.

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?

Explicit 'comece por aqui' entry-point guidance, an explicit exclusion with the alternative to use instead ('se for tese complexa ou nova, chame contexto_ler(o_que="inicio")'), and a mandatory-parameter instruction ('Passe SEMPRE tribunal_da_causa'). When-to-use, when-not-to-use and the fallback are all present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.