Skip to main content
Glama

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

Catálogo de las 22 situaciones del inquilino

catalogo_situaciones_alquiler
Read-only

Devuelve las situaciones de alquiler que conoce la web —el desahucio por impago, la expiración del plazo, el precario, las obras, el monitorio de rentas, los gastos indebidos, la fianza, la subida de renta, la habitación, el subarriendo, la venta de la vivienda, la muerte o el divorcio del arrendatario— con lo que pasa en cada una, qué se puede pedir, su artículo y su plazo, y si tiene escrito en escrito_alquiler o no. Es la lista cerrada: no inventes un identificador. 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_situaciones_alquiler"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only, closed-world, and non-destructive, and the description adds valuable context beyond that: it explains what is returned per situation, that the list is closed, and that no personal data (name, DNI, address, contact) is requested or returned. This privacy constraint is especially useful for an agent deciding what not to pass or ask for.

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 purpose is front-loaded and the description is generally efficient, but the long em-dash enumeration of situations and the repeated privacy warning make one dense paragraph. The details earn their place, though the privacy instruction is stated twice in slightly different ways.

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 parameters, no output schema, and annotations covering safety, the description does the necessary work: it explains the return content, the closed nature of the catalog, the relation to `escrito_alquiler`, and the no-personal-data rule. An agent has enough information to call it correctly and understand what it will get.

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?

There are zero parameters, so the baseline is 4. The description appropriately notes that personal data fields are not among its fields and must not be included in the call, which reinforces the empty schema without needing parameter-level documentation.

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 situaciones de alquiler, and immediately explains the catalog contains what happens, what can be requested, article, deadline, and whether an escrito exists. The closed-list warning and references to `escrito_alquiler` distinguish it from the drafting sibling.

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 clearly signals usage context by saying it is the closed list and that the agent must not invent an identifier; it also links the output to `escrito_alquiler` by indicating which situations have a written document. It does not explicitly state when to use this instead of other catalog tools, but the rental-specific scope is clear.

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