Skip to main content
Glama

salud_feed

Read-only

Check whether the TransMilenio feed is current and review its availability and outage history across a configurable number of days.

Instructions

Si el feed de TransMilenio está al día y cuándo ha estado caído (disponibilidad y caídas).

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

Input Schema

NameRequiredDescriptionDefault
diasNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/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 useful behavioral context in that it returns both current freshness and historical outage information, but it does not say what threshold defines 'al día', how the outage history is aggregated, or what shape the response takes.

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?

A single compact sentence with the core purpose front-loaded and no filler. The parenthetical restatement ('disponibilidad y caídas') is slightly redundant but reinforces scope rather than 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?

With one optional parameter, no output schema, and read-only annotations, the description covers the essentials of what the tool reports. It leaves gaps on the meaning of 'al día', the lookback semantics of 'dias', and the granularity of the outage data, which matter for calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the single 'dias' parameter, so an agent gets no explanation that it is a lookback window measured in days or what the default of 3 implies for the returned outage history. The phrase 'cuándo ha estado caído' hints at a historical scope but does not tie back to the parameter.

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 (the TransMilenio feed) and states what it reports: whether the feed is current and when it has been down (availability and outages). That is clearly distinguishable from sibling tools like llegadas or paraderos_cerca, though it never contrasts itself with the potentially overlapping estado_sistema.

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: an agent can infer this is the tool to call when it needs to know feed freshness or outage history. There is no explicit when-to-use statement, no mention of estado_sistema as an alternative, and no stated prerequisites or exclusions.

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