Skip to main content
Glama

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

buscar_fundamentacao

Read-only

SUPER-FERRAMENTA DE FUNDAMENTAÇÃO JURÍDICA: recebe um assunto ou tema e reúne, em uma única chamada compactada, legislação federal pertinente, súmulas/temas vinculantes, jurisprudência selecionada e acórdãos da base nacional com identificadores exatos para aprofundamento. Ideal para abrir uma tese completa antes de conferir os dispositivos e julgados escolhidos com pesquisa_juridica. No plano Grátis permite até 2 usos a cada 5 horas; nos planos Essencial e Profissional é liberada dentro da cota do plano.

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": {
      "assunto": "<assunto>"
    },
    "name": "buscar_fundamentacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
assuntoYes
diplomaNo
tribunal_da_causaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, so the safety profile is covered. The description adds genuinely new behavioral context: results are compacted into a single call, include exact identifiers for follow-up, and are rate-limited to 2 uses per 5 hours on the free plan. It does not describe result volume or truncation behavior, keeping it short of a 5.

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 core action and scope, then usage guidance, then quota constraints — a sensible order with no filler sentences. The 'SUPER-FERRAMENTA' framing is promotional but does not obscure meaning.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the safety profile is covered by annotations. However, for a 3-parameter tool with zero schema description coverage, the unexplained 'diploma' and 'tribunal_da_causa' parameters leave a real gap an agent must guess at.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only clarifies 'assunto' ('recebe um assunto ou tema'). The 'diploma' and 'tribunal_da_causa' parameters are never mentioned, leaving two of three parameters undocumented in both schema and description.

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: receives a subject/theme and gathers federal legislation, súmulas/binding themes, selected case law and national-database rulings with exact identifiers. It also explicitly distinguishes itself from pesquisa_juridica, so an agent can tell the two apart without opening either 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?

Gives explicit when-to-use guidance ('Ideal para abrir uma tese completa antes de conferir os dispositivos e julgados') and names the alternative tool (pesquisa_juridica) for the follow-up verification step. It also states plan-based availability, which affects whether the agent should call it at all.

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.