Skip to main content
Glama

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

contexto_ler

Read-only

CONTEXTO DO ADVOGADO (somente leitura; não conta na cota). o_que="inicio" (padrão) devolve de uma vez: os estilos de peça disponíveis, a memória (planos Essencial, Profissional e Escritório) e o uso do plano. Chame no começo da conversa e SEMPRE antes de redigir uma peça. Passe chave=<número CNJ ou nome do cliente> para ver o que já se sabe daquele caso. Outros valores: "memoria" (chave, ou consulta=), "estilo" (nome_estilo="padrao" ou o nome de um estilo dele: devolve o guia de tipografia, estrutura e como citar, que você deve seguir à risca; sem nome, lista os estilos), "estilo_json" (o estilo como JSON, para editar), "limite" (quanto do plano foi usado, em %, e quando renova), "manual" (como usar o Elden; assunto = memoria | estilo | citacao | tribunais | limites | planos | tudo).

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": "contexto_ler"
  }
}

Input Schema

NameRequiredDescriptionDefault
chaveNo
o_queNoinicio
assuntoNo
consultaNo
nome_estiloNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 the non-obvious behavioral fact that calls don't consume plan quota, and it distinguishes the estilo mode's guidance ('que você deve seguir à risca') from a mere listing. It doesn't discuss any failure modes, but for a read-only tool that is a minor gap.

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-loads the read-only/no-quota constraint and the default behavior before the mode catalog, and every clause carries information. The mode catalog is crammed into one long sentence with parenthetical nesting, which costs some scannability.

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?

An output schema exists, so return values need not be described, and the description still sketches what each mode yields. For a five-parameter, zero-coverage read tool, an agent has everything needed to pick a mode and pass the right arguments.

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 coverage is 0% and all five parameters are undescribed in the schema, so the description carries the full burden — and it does: chave accepts a CNJ number or client name, o_que's valid values are enumerated with the default, consulta is tied to the memoria mode, and nome_estilo is explained with its no-argument fallback. No schema-level enum exists, so listing the accepted values here is genuinely load-bearing.

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+resource (read the lawyer's context) and enumerates exactly what the default mode returns: piece styles, memory across three plan tiers, and plan usage. The 'somente leitura; não conta na cota' framing also separates it from the write-side sibling (contexto_gravar) without needing the schema.

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?

Gives unusually strong when-to-use guidance: 'Chame no começo da conversa e SEMPRE antes de redigir uma peça', plus the conditional 'Passe chave=... para ver o que já se sabe daquele caso'. It stops short of naming an alternative tool or stating when not to use it, so it falls below the explicit-alternatives bar.

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.