Skip to main content
Glama

Próceres · escritos judiciales de España: papeleta, demanda y recursos

Catálogo de ilegalidades del expediente de justicia gratuita

catalogo_impugnaciones_justicia_gratuita
Read-only

Devuelve la ficha completa de cada ilegalidad que la herramienta impugnacion_justicia_gratuita sabe contestar: el identificador, la categoría, la fase del procedimiento con lo que la Administración está obligada a hacer y el plazo que tiene, qué pasa si vence sin respuesta, qué escrito la resuelve con su prioridad y su ventanilla, qué hay que probar y qué pasa si no se actúa. Es la única lista válida de identificadores: no inventes ninguno. La ficha completa (y no una lista plana) es lo que permite decidir cuál es la ilegalidad del caso. No pide ni devuelve datos personales: el nombre, el DNI, el domicilio y el contacto NO están entre sus campos (el escrito los deja como huecos entre corchetes para que los rellene quien lo presenta). No le pidas esos datos y no los escribas en la llamada.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, closed-world, non-destructive), and the description adds real substance: the exact fields returned per entry (id, categoría, fase, obligación y plazo de la Administración, efectos del silencio, escrito y prioridad/ventanilla, prueba exigida) and the guarantee that no personal data is requested or returned. Volume/ordering of the list is unspecified but is secondary here.

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 what is returned and why it matters, followed by the identifier-authority rule and the privacy constraint. Slightly long and mildly repetitive (the personal-data point is stated twice: 'no pide ni devuelve datos personales' and 'no le pidas esos datos'), but every part is actionable.

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

Completeness4/5

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

For a zero-parameter, no-output-schema catalog, the description supplies what the schema cannot: the content of each record, the authority of its identifiers, and the data it must never carry. The only missing piece an agent would want is how this catalog relates to the other AJG catalogs among the siblings.

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

Parameters4/5

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

Zero parameters, so the schema baseline is 4. The description reinforces this by stating explicitly that name, DNI, domicilio and contact are not fields and must not be passed in the call, which prevents an agent from fabricating arguments for a no-arg tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Devuelve la ficha completa de cada ilegalidad') and pins the scope to what the sibling `impugnacion_justicia_gratuita` can answer, so an agent knows what it gets. It does not differentiate itself from the closely-named catalog siblings (catalogo_ilegalidades_ajg, catalogo_motivos_denegacion_ajg), which is the one gap.

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?

Makes the use case explicit: the full fichas (not a flat list) are what let you decide which ilegalidad applies to the case, i.e. call this before building an impugnación. It also gives concrete prohibitions ('no inventes ninguno' de identificadores, don't request or write personal data). It stops short of naming when to use the other catalogo_* tools instead.

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.

Resources