Skip to main content
Glama

Find cars and prices

buscar_disponibilidad
Read-only

Searches available cars and final prices for given dates and Tenerife offices. Returns only Canarias.com's own fleet. The enlaceBusquedaWeb field contains the complete website price list. The modoEnlace field identifies the configured continuation mode. The price includes full insurance with no excess (drivers aged 23 or over, subject to terms). Each offer also shows the deposit. Each result includes precioOnline (advance online payment, 10% online payment discount; null when only pay at pickup is available), precioEnOficina (standard rate, paid at pickup), ahorroOnline (precioEnOficina minus precioOnline, computed by the engine) and, when available, resumenPrecio (ready-made text with both prices). Online payment is optional; prepaid rentals can be cancelled free of charge up to 24 hours before pickup, with a refund. The deposit guarantees the car is returned on time.

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": {
      "oficinaRecogida": "<oficinaRecogida>",
      "oficinaDevolucion": "<oficinaDevolucion>",
      "recogida": "<recogida>",
      "devolucion": "<devolucion>"
    },
    "name": "buscar_disponibilidad"
  }
}

Input Schema

NameRequiredDescriptionDefault
edadNoDriver age, 21 to 85
recogidaYesLocal pickup date and time, YYYY-MM-DDTHH:mm
devolucionYesLocal drop-off date and time, YYYY-MM-DDTHH:mm
oficinaRecogidaYesNumeric pickup office ID
oficinaDevolucionYesNumeric drop-off office ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / devolucion / description
      Previous value: -"Fecha y hora local YYYY-MM-DDTHH:mm / Local drop-off date and time"New value: +"Local drop-off date and time, YYYY-MM-DDTHH:mm"
    • changedInput schema / properties / edad / description
      Previous value: -"Edad del conductor, de 21 a 85 años / Driver age, 21 to 85"New value: +"Driver age, 21 to 85"
    • changedInput schema / properties / oficinaDevolucion / description
      Previous value: -"ID numérico de la oficina de devolución / Numeric drop-off office ID"New value: +"Numeric drop-off office ID"
    • changedInput schema / properties / oficinaRecogida / description
      Previous value: -"ID numérico de la oficina de recogida / Numeric pickup office ID"New value: +"Numeric pickup office ID"
    • changedInput schema / properties / recogida / description
      Previous value: -"Fecha y hora local YYYY-MM-DDTHH:mm / Local pickup date and time"New value: +"Local pickup date and time, YYYY-MM-DDTHH:mm"
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered; the description goes further by disclosing fleet scope, that prices include full insurance with no excess for drivers 23+, that a deposit is shown, that precioOnline can be null when only pay-at-pickup is available, and that prepaid bookings are cancellable free up to 24h before pickup. Missing only operational traits such as error behavior or result volume limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body drifts into payload-field explanations (enlaceBusquedaWeb, modoEnlace, ahorroOnline, resumenPrecio) before the more decision-relevant pricing and cancellation terms. The closing line about the deposit's purpose ('guarantees the car is returned on time') is filler for tool-selection purposes.

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?

With no output schema, the description carries the return-value burden and does so thoroughly (precioOnline vs precioEnOficina, computed savings, ready-made price text). It is nearly complete for a read-only search; only the wiring to buscar_oficinas for valid office IDs is unstated.

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 100% (each parameter is described in the schema), so baseline is 3. The description adds one genuinely new constraint not in the schema: the no-excess insurance applies to drivers aged 23 or over, which qualifies the edad parameter's practical effect; it adds nothing about office ID provenance or date format beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource ('Searches available cars and final prices') plus scope ('given dates and Tenerife offices'), and adds 'Returns only Canarias.com's own fleet' to constrain the result set. It is clear enough to distinguish from an office lookup like buscar_oficinas, though it never names ver_oferta or crear_enlace_reserva to sharpen the boundary.

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

Usage Guidelines2/5

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

The description implies a search flow (dates plus pickup/drop-off offices) but never states when to use this tool versus the sibling tools, nor any exclusions or prerequisites such as where office IDs come from. Usage must be inferred entirely from the name and parameters.

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