Skip to main content
Glama

Condiciones del alquiler

consultar_condiciones
Read-onlyIdempotent

Fianza, seguro, kilometraje, combustible, requisitos del conductor, antelación mínima, días mínimos y máximos, pago, cancelación y extras con su precio.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered and the description introduces no contradiction. With no output schema, the description's field list does usefully signal what comes back, but it says nothing about whether the terms are global or vehicle-specific, how they are formatted, or any caveats.

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?

It is a single compact fragment with no wasted words, but it is an unstructured comma-separated list with no lead clause explaining what the tool does. Efficiency is achieved at the cost of readability and front-loading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument read tool with no output schema, the description suffices to convey the topics returned, which is its main job. However, it leaves open whether conditions are universal or depend on a selected vehicle, which matters given the sibling buscar_vehiculos.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema; the baseline of 4 applies. No parameter-level information is missing or misleading.

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

Purpose3/5

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

The description is a bare noun list of condition topics (deposit, insurance, mileage, fuel, driver requirements, minimum advance, min/max days, payment, cancellation, extras) rather than a verb-plus-resource statement; the verb only exists in the name 'consultar'. The enumerated scope does let an agent infer it returns general rental terms and distinguishes it from buscar_vehiculos or calcular_presupuesto, but the framing never states the action explicitly.

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 when-to-use guidance, no exclusions, and no reference to alternatives such as buscar_vehiculos or calcular_presupuesto. The agent must guess the trigger condition (e.g. before booking, to explain terms to a customer) entirely on its own.

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