Skip to main content
Glama
danilat
by danilat

zaragoza-bus-estimations

Check real-time bus arrival estimates for Zaragoza stops. Enter a stop number to get upcoming bus times.

Instructions

Get the estimation of when a bus arrives to a stop in Zaragoza in realtime

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stopYes

Implementation Reference

  • Handler function that fetches real-time bus arrival estimations for a given stop ID from the DNDzgz API and returns the data as JSON or an error message.
    async ({ stop }) => {
      const response = await fetch(
        `https://dndzgz.herokuapp.com/services/bus/${stop}`
      );
      if (response.ok) {
        const data = await response.json();
        return {
          content: [{ type: "text", text: JSON.stringify(data) }],
        };
      } else {
        return {
          content: [
            {
              type: "text",
              text: `Is not possible to get the estimate for the stop ${stop}`,
            },
          ],
        };
      }
    }
  • Input schema defining the 'stop' parameter as a number.
    { stop: z.number() },
  • index.js:102-126 (registration)
    Registration of the 'zaragoza-bus-estimations' tool with name, description, input schema, and handler function using server.tool().
    server.tool(
      "zaragoza-bus-estimations",
      "Get the estimation of when a bus arrives to a stop in Zaragoza in realtime",
      { stop: z.number() },
      async ({ stop }) => {
        const response = await fetch(
          `https://dndzgz.herokuapp.com/services/bus/${stop}`
        );
        if (response.ok) {
          const data = await response.json();
          return {
            content: [{ type: "text", text: JSON.stringify(data) }],
          };
        } else {
          return {
            content: [
              {
                type: "text",
                text: `Is not possible to get the estimate for the stop ${stop}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool provides 'realtime' estimations, which hints at dynamic data, but does not cover critical aspects such as data freshness, rate limits, error handling, authentication needs, or response format. For a real-time data tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, with every part contributing to understanding the core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (real-time data retrieval), lack of annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It does not address how estimations are returned, what data is included, or potential limitations, making it inadequate for effective agent use.

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?

The input schema has 1 parameter with 0% description coverage, and the description does not add any semantic information about the 'stop' parameter. It does not explain what 'stop' represents (e.g., stop ID, name, or code), valid ranges, or examples. With low schema coverage, the description fails to compensate, leaving the parameter poorly documented.

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 clearly states the tool's purpose: 'Get the estimation of when a bus arrives to a stop in Zaragoza in realtime.' It specifies the action ('get the estimation'), resource ('bus'), and scope ('Zaragoza'), distinguishing it from sibling tools like zaragoza-bizi-estimations (bikes) and zaragoza-tram-estimations (trams). However, it doesn't explicitly differentiate from zaragoza-bus-stops, which might be related but serves a different function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like zaragoza-bus-stops (which might list stops) or other estimation tools for different transport modes, nor does it specify prerequisites or exclusions. Usage is implied by the purpose but lacks explicit context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danilat/mcp-dndzgz'

If you have feedback or need assistance with the MCP directory API, please join our Discord server