Índices AR

Actualizar un alquiler por ICL, IPC o UVA

actualizar_alquiler

Calcula el cronograma de actualizaciones de un alquiler: a partir del monto inicial, la fecha de inicio, el índice (ICL, IPC o UVA) y cada cuántos meses se ajusta, devuelve el monto vigente en cada período hasta la fecha de consulta y el próximo ajuste. Cada período se ajusta por la variación del índice entre el inicio del período anterior y el inicio del nuevo. Costo: 3 crédito(s).

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": {
      "monto_inicial": "<monto_inicial>",
      "fecha_inicio": "<fecha_inicio>"
    },
    "name": "actualizar_alquiler"
  }
}

Input Schema

Name	Required	Description	Default
`indice`	No		icl
`fecha_inicio`	Yes	Inicio del contrato, YYYY-MM-DD
`monto_inicial`	Yes	Alquiler del primer mes, en pesos
`fecha_consulta`	No	Hasta qué fecha calcular. Por defecto hoy.
`periodicidad_meses`	No	Cada cuántos meses se actualiza (3, 4, 6, 12)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose valuable behavior: the per-period adjustment formula, that output extends to the query date plus the next adjustment, and a credit cost of 3. It does not state what happens when the start date is in the future, when a period crosses a date with no published index, or whether the operation has any side effects beyond consuming credits.

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?

Three sentences, front-loaded with purpose, then the calculation rule, then the cost — each sentence adds information. Dense but efficient; only the cost sentence feels slightly tacked on.

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 a 5-parameter calculation tool with no output schema and no annotations, the description communicates inputs, the computation rule, the shape of the result (per-period amount plus next adjustment), and pricing. Remaining gaps — output formatting, missing-index handling, and invalid date behavior — are real but secondary for a stateless calculation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the input schema already documents most parameters including the index enum and dates. The description mentions all five conceptually and adds the semantic relationship between periodicidad and the per-period index variation, but provides no extra format or edge-case detail beyond the schema. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ("Calcula el cronograma de actualizaciones de un alquiler") and then names the exact inputs and outputs, so the agent knows this produces a full schedule rather than a single adjusted amount. The stated calculation rule (index variation between the start of the previous period and the start of the new one) further separates it from a one-off adjustment tool like ajustar_monto.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The use case is implied clearly by the purpose (get a full rent-update schedule), but there is no explicit when-to-use vs. alternative guidance — nothing tells the agent to prefer ajustar_monto or indice_valor for simpler needs. No preconditions or exclusions are stated.

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

All Índices AR 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?