Skip to main content
Glama

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

Reclamación de lo cobrado de más por el alquiler: renta por encima del tope, subida ilegal o sobreprecio de una habitación

reclamacion_alquiler
Read-only

Compone la reclamación del dinero cobrado de más por el alquiler, con el mismo motor que la web: la renta por encima del precio máximo de una zona tensionada, la subida por encima del IRAV, el sobreprecio de una habitación alquilada por el dueño y el de la habitación subarrendada (art. 8.2 y 17.9 LAU), con lo cobrado sin causa (art. 6 LAU). Se le dan rentas, superficies, meses y respuestas de sí/no; el nombre de quien reclama y el del arrendador van como huecos. Si con esos datos no hay exceso que reclamar, la herramienta lo dice y no compone un papel que pida de más. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "renta": "<renta>"
    },
    "name": "reclamacion_alquiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccaaNoLa comunidad autónoma, si aplica su propio índice o norma.
tipoNoQué se alquila.
irravNoEl IRAV vigente, en porcentaje.
mesesNoCuántos meses se lleva pagando de más.
rentaYesLa renta mensual que se paga, tal cual («750»).
rentaTotalNoLa renta del contrato unitario de la vivienda completa.
tensionadaNoSi el municipio está declarado zona de mercado residencial tensionado.
fechaInicioNoLa fecha de inicio del contrato (AAAA-MM-DD).
granTenedorNoSi el arrendador es gran tenedor (art. 3.k Ley 12/2023).
habitacionesNoCuántas habitaciones se alquilan a la vez en la vivienda.
precioIndiceNoEl precio máximo del sistema de índices, si se conoce.
contratoNuevoNoSi el contrato se firmó a partir del 26/5/2023.
rentaAnteriorNoLa última renta del contrato anterior en la misma vivienda.
consentimientoNoSi hay consentimiento escrito del arrendador para el subarriendo.
superficieTotalNoLa superficie total de la vivienda, si se conoce.
arrendadorJuridicaNoSi el arrendador es persona jurídica.
superficieHabitacionNoLa superficie de la habitación, si se conoce.
quienAlquilaLaHabitacionNoSi es una habitación: si la alquila el dueño o un inquilino que subarrienda (art. 8.2 LAU).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a non-destructive read operation, and the description still adds substantial behavior the agent could not infer: it runs the same engine as the web, it self-limits by refusing to draft a demand with no legal excess, and it defines the placeholder convention for names in the output document. That refusal path is exactly the kind of trait that prevents an agent from calling it in the wrong situation.

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 the scenarios and the mechanism, then the input hints, then the refusal rule, then the data-privacy constraint — a sensible order. The privacy point is restated twice (once descriptively, once as an imperative), which is mild redundancy in an otherwise dense, purposeful passage.

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 an 18-parameter tool with no output schema, the description covers the trigger, the input family, the refusal behavior, and the placeholders left in the generated paper. It does not say what form the composed document is returned in (plain text, structured sections, etc.), which is the one thing an agent might still need to know before calling.

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%, so the 18 field descriptions already carry the baseline. The description still adds value by grouping what the inputs represent (rentas, superficies, meses, respuestas sí/no) and, more importantly, by stating which data is deliberately absent from the field set — nombre, DNI, domicilio, contacto — so the agent knows not to invent or request them. It does not explain how the yes/no/«duda» tri-states change the legal reasoning, which keeps it from a 5.

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 artifact (componer la reclamación) plus the precise scope: four enumerated overcharge scenarios (renta sobre tope en zona tensionada, subida sobre IRAV, sobreprecio de habitación por el dueño, y subarriendo art. 8.2/17.9 LAU) más lo cobrado sin causa (art. 6 LAU). That enumeration lets an agent distinguish it from sibling generators such as escrito_alquiler or catalogo_situaciones_alquiler without opening the 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?

The conditions for use are clear — you call it when there is an overcharge to claim, and the description explicitly says that if the supplied figures produce no excess the tool reports that and does not compose a document. It also constrains the call by forbidding personal data. It stops short of naming an alternative sibling for the cases it declines, so it is strong but not fully comparative.

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