Skip to main content
Glama

historial_ruta

Read-only

Compare scheduled and observed service for a TransMilenio route over recent days, including average/max buses, average delay, and hourly performance.

Instructions

Cómo le ha ido a una ruta en los últimos días: buses promedio y máximo, viajes vistos contra programados, retraso promedio y el perfil por hora. fecha es el último día.

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": {
      "ruta": "<ruta>"
    },
    "name": "historial_ruta"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNo
rutaYes
fechaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuine behavioral context by disclosing the returned metric set and the crucial detail that `fecha` is the *last* day of the window rather than the first. It does not mention data freshness, coverage limits, or what happens when no trips were recorded in the window.

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?

Two compact sentences with the metric inventory front-loaded and the `fecha` semantic clarification at the end; nothing is padded. The comma-separated metric list is dense but each item corresponds to real output content that compensates for the absent output schema.

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?

Because there is no output schema, describing the returned metrics is necessary and done well, and the read-only profile is covered by annotations. However, with three undocumented parameters the description leaves the required `ruta` identifier format and the exact `dias`-versus-`fecha` window interaction ambiguous, which is a meaningful gap for a reporting call.

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, and it only clarifies one of three: `fecha` is defined as the final day of the range. `dias` is only obliquely covered by 'últimos días' (its default of 7 lives in the schema), and `ruta` — the sole required parameter — is never defined as an ID, code, or name.

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 (una ruta) and enumerates the specific outputs — buses promedio y máximo, viajes vistos vs programados, retraso promedio, perfil por hora — so an agent knows this is a retrospective route-performance report. It does not explicitly contrast with siblings like `buses_ruta` or `programacion_ruta`, so the boundary is inferable but not stated.

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 only implied by 'en los últimos días' and the `fecha`/`dias` window, which signals historical analysis rather than live state. There is no explicit when-to-use vs when-not, and no mention of alternatives such as the live-bus or schedule tools, so the agent must infer the routing decision itself.

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