Skip to main content
Glama

nexus_consulta

Answer concrete legal questions in natural language with certainty locks and normative references. Supports conversational threads and optional reference documents.

Instructions

CONSULTA JURÍDICA LIBRE (Nodo A — modo Q&A). Pregunta jurídica en lenguaje natural, con o sin documento de referencia. Devuelve respuesta con candados de certeza y referencias normativas/jurisprudenciales cuando aplican. Soporta hilos conversacionales mediante el parámetro history. Coste: 1 crédito. USAR CUANDO: el usuario hace una pregunta jurídica concreta (¿cuál es el plazo de prescripción?, ¿es válida esta cláusula?, ¿qué dice el TS sobre X?) y NO necesita análisis íntegro de un documento.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesPregunta jurídica concreta del operador. Puede ir respaldada por un documento de contexto (`documentText`) o por un análisis previo (`analysisContext`).
jurisdictionNoCódigo ISO de la jurisdicción que rige la consulta. Soporta US-CA/US-NY etc. y MULTI.ES
documentTextNoTexto del documento de referencia (opcional). Si se aporta, el modelo lo trata como Capa A y cita literalmente.
analysisContextNoAnálisis Nodo A previo sobre el documento (opcional). Si se aporta, sirve como contexto para razonar sobre el caso.
languageNoes
historyNoHistorial conversacional opcional. Permite múltiples turnos sobre el mismo caso.
Behavior3/5

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

With no annotations, the description carries full burden. It mentions returning certainty locks and references, supporting conversational history, and cost. But lacks details on rate limits, auth, or edge cases. Decent but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single paragraph that front-loads purpose but includes some redundancy (e.g., 'con o sin documento de referencia' and subsequent param mentions). Could be more concise.

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?

Given 6 parameters, no output schema, and no annotations, description covers usage context and basic behavior but omits return format, error handling, and limitations. Adequate but incomplete.

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

Parameters3/5

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

Schema coverage is 83%, so baseline is 3. Description adds minor context for the history parameter but otherwise doesn't extend beyond 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?

The description clearly defines the tool as a free legal Q&A (Nodo A) answering concrete legal questions in natural language, with examples. It distinguishes from siblings by specifying when NOT to use (full document analysis).

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?

Provides explicit when-to-use condition (concrete legal question, no full document analysis) and mentions cost (1 crédito). However, it doesn't explicitly name sibling tools that should be used instead.

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/djtellado/nexus-legal-mcp'

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