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

Lo que el abogado y el procurador deben a su cliente: información, notificaciones, documentación, cuentas y reclamaciones

deberes_del_abogado

Read-only

Devuelve el mapa de los deberes del profesional de la abogacía con su cliente —antes del encargo, mientras lleva el asunto, al terminar o al cambiar de abogado, y si algo va mal—, cada uno con las palabras de la Ley Orgánica 5/2024, del Derecho de Defensa, y del Estatuto General de la Abogacía Española (Real Decreto 135/2021), y las reglas de los honorarios (libres, sin baremos: art. 14 de la Ley 2/1974); y el de los deberes del procurador con su poderdante —tenerle al corriente y darle cuenta de las notificaciones (arts. 26.2 y 28.1 LEC), entregarle lo recibido (art. 27 LEC y 1720 CC), las grabaciones (art. 147 LEC), rendir cuentas (art. 38.2.b del Estatuto General de los Procuradores, Real Decreto 1281/2002) y su responsabilidad disciplinaria ante el Colegio (arts. 59 y 60 EGP, 546.3 LOPJ)—. Dice cuáles cumple siempre y cuáles nacen de que el cliente los pida, y qué escritos compone escrito_al_abogado. Sin profesional, los dos. 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": "deberes_del_abogado"
  }
}

Input Schema

Name	Required	Description	Default
`profesional`	No	De quién: «abogado» o «procurador». Sin él, el mapa de los dos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / profesional

Added value: +{
+  "description": "De quién: «abogado» o «procurador». Sin él, el mapa de los dos.",
+  "enum": [
+    "abogado",
+    "procurador"
+  ],
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond them: it states no personal data is requested or returned, explains that names/DNI/address are left as bracketed blanks in the generated document, and instructs the caller not to pass such data — a privacy trait the annotations do not convey.

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?

The purpose is front-loaded, but the opening sentence sprawls across dozens of nested statutory citations (LO 5/2024, RD 135/2021, art. 14 Ley 2/1974, arts. 26.2/27/28.1 LEC, RD 1281/2002), which thickens the text without helping tool selection. The trailing privacy constraint is well placed, but the middle of the description is denser than necessary.

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?

There is no output schema, so the description must convey what comes back, and it does: a map of duties with the statutory wording, split into always-applicable vs client-requested duties, for one or both professions. That is adequate for a single-optional-parameter read-only lookup; only finer return-shape details (e.g. grouping or ordering) are left implicit.

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?

Schema coverage is 100% with a single enum parameter, so the baseline would be 3. The description adds value by emphasizing that the personal-data fields are explicitly NOT among its inputs and by restating the default ('the map of both'), which guards against a common agent error of trying to supply client identifiers.

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?

Uses a specific verb+resource ("Devuelve el mapa de los deberes del profesional de la abogacía con su cliente") and enumerates both covered roles (abogado, procurador) plus the temporal scope. It also distinguishes itself from the sibling `escrito_al_abogado`, which composes the actual filings, so an agent can separate the two 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation context (before the engagement, during the matter, on termination, on change of lawyer, "si algo va mal") and states the default behavior when `profesional` is omitted ("Sin `profesional`, los dos"). It points to `escrito_al_abogado` for the documents themselves, though it never says explicitly when another tool would be a better choice.

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?