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

Las vías de impugnación del taller de Casos

catalogo_vias_procesales

Read-only

Devuelve las 161 vías procesales del taller de Casos —reposición, revisión, apelación, suplicación, casación, queja, amparo, error judicial…, de todos los órdenes— con su id, contra qué resolución caben, ante quién se presentan y su plazo. Para cada vía dice además las situaciones que la web argumenta (qué se le reprocha a la resolución), con la clave de escrito_procesal. Es la única lista válida de ids para escrito_de_via. 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_vias_procesales"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: fixed catalog size (161), the exact per-entry payload including the `escrito_procesal` key, and an explicit privacy boundary (no personal data withheld or returned, placeholders filled by the filer). No pagination or refresh behaviour is mentioned, but for a static read-only catalog that is a minor omission.

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?

The payload description is front-loaded and specific, with the id-uniqueness constraint placed prominently. The closing sentences about personal data are somewhat repetitive (reiterating twice that name/DNI/address/contact are absent), which costs a point but the redundancy serves a safety purpose.

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?

With no output schema and no parameters, the description carries the full burden and discharges it: it names the catalog, its size, every returned field, the linkage key to `escrito_de_via`, and the privacy constraint. An agent has everything needed to call it correctly and interpret the result.

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?

The tool takes zero parameters, so the baseline is 4. The description reinforces this by stating it neither asks for nor accepts personal data, telling the agent not to attempt to pass any arguments.

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 ('Devuelve las 161 vías procesales del taller de Casos'), enumerates the actual content (reposición, revisión, apelación, casación, amparo…) and the fields each entry carries (id, resolución, órgano, plazo). It also differentiates itself from the sibling catalogs by declaring it is 'la única lista válida de ids para escrito_de_via'.

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 clear routing context: this is the id source to use before calling `escrito_de_via`, and it explicitly forbids requesting or supplying personal data. It does not, however, contrast itself with the neighbouring catalogs (`catalogo_escritos_procesales`, `catalogo_del_taller`), so an agent must infer which catalog to pick when the request is ambiguous.

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

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

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?