Skip to main content
Glama

Calcular presupuesto

calcular_presupuesto
Read-onlyIdempotent

Precio exacto de un alquiler (mismo cálculo que la web) para un vehículo, un punto y unas fechas en hora de Madrid, con extras opcionales (ids de consultar_condiciones, formato id:cantidad), desglose, total con IVA y bookingUrl para que el usuario revise y envíe la reserva en la web con esos extras ya marcados.

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": {
      "vehiculo": "<vehiculo>",
      "punto": "<punto>",
      "fecha_recogida": "<fecha_recogida>",
      "hora_recogida": "<hora_recogida>",
      "fecha_devolucion": "<fecha_devolucion>",
      "hora_devolucion": "<hora_devolucion>"
    },
    "name": "calcular_presupuesto"
  }
}

Input Schema

NameRequiredDescriptionDefault
edadNoFranja de edad del conductor: 21-24, 25-29 o 30+.30+
puntoYesPunto de recogida.
extrasNoExtras opcionales (ids de las condiciones), con formato id:cantidad separados por comas.
vehiculoYesId del vehículo (de /api/v1/vehiculos).
hora_recogidaYesHH:MM, hora de Madrid.
fecha_recogidaYesAAAA-MM-DD, hora de Madrid.
hora_devolucionYes
fecha_devolucionYes
punto_devolucionNoPunto de devolución (por defecto, el de recogida).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: the price matches the website exactly, times are Madrid-local, IVA is included in the total, and the returned bookingUrl has the chosen extras pre-selected — details an agent cannot derive from annotations.

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?

A single sentence, but it is front-loaded with the core purpose (exact price) and then the inputs, the extras convention and the outputs. It is dense without wasted clauses, though the run-on structure makes the return-value portion easy to skim past.

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 read-only calculator with no output schema, the description covers what comes back (breakdown, total with IVA, bookingUrl) and the key conventions (Madrid time, extras format, quotes are not bookings). Minor gaps remain, such as currency and behavior on unavailable vehicles or invalid date ranges.

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 78%, so most parameters are self-documenting, and the description reinforces the two weakest ones: it specifies that extras are condition ids in id:cantidad form sourced from consultar_condiciones, and that dates/times are Madrid-local, which backfills the undocumented fecha_devolucion and hora_devolucion fields.

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 action and scope: returns the exact rental price, identical to the website calculation, for a vehicle, pickup point and dates in Madrid time. It also names the return payload (breakdown, total with IVA, bookingUrl), so an agent can distinguish it from price-discovery or search siblings 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?

Implies a clear workflow: quote first, then the user reviews and completes the booking on the web via bookingUrl, and extras ids must come from consultar_condiciones. It gives strong positive context but never states when not to use it or how it differs from a plain vehicle search.

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