Skip to main content
Glama

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

Los 13 motivos por los que se impugna la resolución de justicia gratuita, con su alegato

catalogo_motivos_denegacion_ajg
Read-only

Devuelve las causas de denegación que de verdad se ven en la jurisprudencia —los umbrales de ingresos del art. 3, los signos externos del art. 4, la vía excepcional del art. 5, la documentación, la falta de motivación, la insostenibilidad, el derecho ex lege, la persona jurídica y el plazo—, cada una con cómo se reconoce en la resolución, el alegato ya redactado que entra en el escrito, su norma y la jurisprudencia que lo respalda. Son los identificadores válidos del campo motivosDenegacion de impugnacion_justicia_gratuita, en el orden en que el escrito los alega. 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_motivos_denegacion_ajg"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 genuinely non-obvious behavior: the tool neither requests nor returns personal data, and the escrito leaves name/DNI/address/contact as bracketed placeholders, plus the ordering of returned entries. The only gap is that it never states the response shape (list vs object) beyond the field-level contents.

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?

Purpose and content are front-loaded in the opening clause, and the closing sentences about personal data are short and purposeful. The long enumerated middle clause (arts. 3, 4, 5, documentation, lack of motivation, insostenibilidad, ex lege, legal person, deadline) is dense but each item is informative rather than filler.

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?

For a zero-parameter, read-only static catalogue with no output schema, the definition supplies what an agent actually needs: what comes back, in what order, how it maps to a sibling tool's parameter, and an explicit prohibition on sending personal data. Nothing material is left unexplained.

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 baseline is 4 and there is nothing for the description to disambiguate. It does add useful cross-tool semantics by tying the output values to a specific input field of another tool, which is meaning beyond the empty 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?

States a specific verb and resource ("Devuelve las causas de denegación") and enumerates exactly what each entry contains: how it is recognized in the resolution, the pre-drafted alegato, its norma and supporting case law. It also names its role relative to siblings by declaring itself the source of valid identifiers for the `motivosDenegacion` field of `impugnacion_justicia_gratuita`, which separates it from `catalogo_ilegalidades_ajg` and `catalogo_impugnaciones_justicia_gratuita`.

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?

The description makes the downstream use case explicit — these are the values to feed into the `motivosDenegacion` field of `impugnacion_justicia_gratuita`, and it specifies the order in which the escrito alleges them, which is actionable guidance. It stops short of an explicit "call this before X" instruction or an exclusion statement against the other two catalogue siblings, so the agent must infer the sequencing.

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