Skip to main content
Glama

View offer details

ver_oferta
Read-only

Returns the details of an offer from Canarias.com's own fleet: car, priced extras, terms, full insurance with no excess included (drivers aged 23 or over, subject to terms) and 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": {
      "idOferta": "<idOferta>"
    },
    "name": "ver_oferta"
  }
}

Input Schema

NameRequiredDescriptionDefault
idOfertaYesOffer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idOferta / description
      Previous value: -"Identificador opaco de la oferta / Opaque offer ID"New value: +"Offer ID"
  2. Changed1 schema field changed
    • changedInput schema / properties / idOferta / description
      Previous value: -"Identificador opaco devuelto por buscar_disponibilidad / Opaque offer ID"New value: +"Identificador opaco de la oferta / Opaque offer ID"
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds behavioral context the annotations cannot: prepaid bookings are refundable up to 24 hours before pickup, online payment is optional, and precioOnline may be null when only pay-at-pickup exists. It does not state failure behavior, e.g. what happens with an invalid or expired offer ID.

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 core return payload, then pricing fields, then the cancellation policy. It is dense but nearly every clause carries real information; the closing sentence about the deposit guaranteeing on-time return is the weakest link and borders on filler.

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 does the heavy lifting by naming each returned field (precioOnline, precioEnOficina, ahorroOnline, resumenPrecio) and explaining how they relate. What remains missing is the acquisition path for idOferta and error/expiry behavior, both of which an agent needs to call this reliably.

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?

One parameter at 100% schema coverage, so the schema already carries the semantics and baseline 3 applies. The description adds no guidance on the format of idOferta or where the caller obtains it, which would be the only meaningful addition 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?

States a specific verb and resource: "Returns the details of an offer from Canarias.com's own fleet," and enumerates what the detail payload contains (car, extras, terms, insurance, deposit), which sharpens the meaning of "offer" here. It does not explicitly contrast with siblings, but the read-only detail scope is unmistakable against buscar_disponibilidad or crear_enlace_reserva.

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?

There is no explicit when-to-use guidance: nothing says this should be called after buscar_disponibilidad, that it is the step before crear_enlace_reserva, or what to do when an offer has expired. Usage is only implied by the presence of a single idOferta parameter; the agent must infer the whole workflow.

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