Skip to main content
Glama

Buscar vehículos

buscar_vehiculos
Read-onlyIdempotent

Flota con precio base por día (IVA incluido), del más barato al más caro, con fotos, categoría, carrocería, equipamiento y descripción. Filtros opcionales por punto, categoría, combustible, cambio y plazas mínimas.

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": "buscar_vehiculos"
  }
}

Input Schema

NameRequiredDescriptionDefault
puntoNoPunto de recogida (id de /api/v1/puntos).
cambioNo
plazasNoPlazas mínimas.
categoriaNoCategoría: economico, compacto, suv, premium, deportivo o furgoneta.
combustibleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the description's added value is the pricing and ordering behaviour: base price per day with VAT included, sorted ascending by price. It does not mention pagination, result limits or empty-result behaviour, which keeps it from a 5.

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

Conciseness5/5

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

Two sentences with no filler, and the most decision-relevant information (price basis and sort order) comes first. Every clause carries information an agent cannot get from the schema alone.

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 output schema, the description takes on the burden of describing the return shape and does so (price, photos, category, body, equipment, description). For a zero-required-parameter read tool with annotations covering safety, nothing essential is missing.

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 60%, and the description enumerates all five filters (punto, categoría, combustible, cambio, plazas mínimas) and clarifies that plazas is a minimum threshold, compensating for the two params (cambio, combustible) left as bare enums in 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 description names the resource (fleet) with specifics: base price per day including VAT, sorted cheapest to most expensive, and the fields returned (photos, category, body type, equipment, description). It does not explicitly state the search verb or differentiate itself from siblings like listar_puntos, but the scope is unambiguous.

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?

It states that all five filters are optional, which implicitly tells the agent the tool can be called with no arguments to list the whole fleet. There is no explicit when-to-use versus alternatives guidance and no exclusions or preconditions.

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