Skip to main content
Glama

alertas

Read-only

Fetch active TransMilenio disruptions—detours, closures, and traffic management plans—and filter them by search text or route code.

Instructions

Alertas vigentes: desvíos, cierres, planes de manejo de tránsito.

Filtra por texto (buscar: "Caracas", "calle 26") o por código de ruta.

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

Input Schema

NameRequiredDescriptionDefault
rutaNo
buscarNo
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/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 a meaningful behavioral qualifier ('vigentes', i.e. only active alerts) but says nothing about result volume, ordering, or how the default 'limite' of 25 affects output.

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 short lines, front-loaded with what the tool returns and then how to narrow it. Every phrase carries information; nothing is padding.

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 simple read-only lookup with no output schema, the description is largely sufficient on what alerts are, but it omits the meaning of 'limite' and any sense of result shape or ordering, which an agent would need to page or size responses sensibly.

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?

With 0% schema description coverage the description must compensate. It explains 'buscar' as free text with concrete examples ('Caracas', 'calle 26') and clarifies that 'ruta' takes a route code, but leaves 'limite' entirely undocumented and does not say whether filters combine with AND or OR.

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 a specific resource and its contents: 'Alertas vigentes: desvíos, cierres, planes de manejo de tránsito', which lets an agent tell this apart from route, stop and schedule siblings. It is clear but does not explicitly name any sibling for contrast.

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: the agent can infer it should call this when looking for active traffic alerts, and the description tells it the two filter modes. There is no explicit when-to-use/when-not guidance or reference to an alternative tool for a different need.

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