Skip to main content
Glama

planear_viaje

Read-onlyIdempotent

Plan a SITP journey between two locations via direct routes or one transfer; accepts stop names, codes, IDs, or coordinates and returns estimated travel times.

Instructions

Planea un viaje en el SITP entre dos lugares: rutas directas o con un transbordo.

origen y destino pueden ser nombres de paradero/estación, códigos, ids o coordenadas "lat,lon" (se buscan paraderos a menos de 600 m). Los tiempos son estimados con el horario programado e incluyen caminatas y una espera típica por transbordo.

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": {
      "origen": "<origen>",
      "destino": "<destino>"
    },
    "name": "planear_viaje"
  }
}

Input Schema

NameRequiredDescriptionDefault
horaNo
fechaNo
origenYes
destinoYes
max_opcionesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description still adds genuine behavioral substance: results are capped at one transfer, times come from the scheduled timetable rather than live data, and they include walking plus a typical transfer wait — all of which affect how the agent should present results. What it omits is what happens when no route is found.

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?

Three compact sentences, front-loaded with the purpose, then input formats, then output semantics. Every clause carries information; nothing is padded.

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?

With no output schema, the description should convey more about the return value than it does — the shape of the route options, how many are returned by default (max_opciones defaults to 5), and the no-route case all go unstated. It is adequate for invocation but thin for interpreting the response.

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 description coverage is 0%, so the description must carry parameter meaning. It does a thorough job for the two required parameters — origen and destino accept stop/station names, codes, ids, or 'lat,lon' coordinates with a 600 m search radius. But hora, fecha, and max_opciones are never explained: formats and what max_opciones actually controls remain undocumented.

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?

The description opens with a specific verb and resource — 'Planea un viaje en el SITP entre dos lugares' — and immediately scopes the output to 'rutas directas o con un transbordo'. That makes it unambiguously a trip-planner, clearly distinct from the point-lookup siblings such as buscar_paraderos or proximos_buses.

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?

Usage is implied by the purpose: plan a trip between two points. There is no explicit when-to-use or when-not-to-use guidance, and notably no mention of proximos_buses as the alternative for real-time arrivals versus this tool's scheduled estimates — a natural exclusion point left unstated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.