Skip to main content
Glama

estado_sistema

Read-only

Check how many buses are currently on the road by system and how fresh the live feed is, so you can verify transit data availability before relying on it.

Instructions

Cuántos buses hay en vía, por sistema, y qué tan fresco está el feed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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. Beyond that the description only hints at return content ('cuántos buses hay en vía, por sistema') and freshness without saying how freshness is measured, whether the counts are real-time or cached, or what happens when the feed is stale.

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 front-loaded sentence with no filler; the two returned facts arrive immediately. It is arguably under-specified rather than padded, which is the rarer failure, but it errs toward brevity.

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 input parameters and no output schema, the description carries the full burden of explaining what comes back, and it only sketches it: 'por sistema' never says which systems exist, and 'qué tan fresco' gives no units or staleness threshold. For a status tool the annotation coverage is adequate, but an agent cannot interpret the response confidently from this text alone.

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 no parameter meaning to convey and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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 concrete resource and two concrete outputs: bus count currently on the road broken down per system, plus feed freshness. That is far more specific than a restatement of the name 'estado_sistema'. It stops short of distinguishing itself from the sibling 'salud_feed', which sounds like it also touches feed health/freshness.

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 'give me an overall snapshot' call from the returned content, but there is no explicit statement of when to prefer it over 'salud_feed' or 'alertas'. No prerequisites, no when-not-to-use conditions.

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