Skip to main content
Glama
danilat
by danilat

zaragoza-bizi-estimations

Check real-time bike availability and free parking slots at Zaragoza Bizi stations to plan your bike-sharing trips.

Instructions

Get the estimation of bikes and free slots in a Bizi station in Zaragoza in realtime

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationYes

Implementation Reference

  • The handler function that implements the tool logic: fetches bike and free slot estimations from the Bizi API for a given station ID and returns the JSON data or an error message.
    async ({ station }) => {
      const response = await fetch(
        `https://dndzgz.herokuapp.com/services/bizi/${station}`
      );
      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 Bizi station ${station}`,
            },
          ],
        };
      }
    }
  • Zod schema for the tool input: requires a numeric 'station' parameter.
    { station: z.number() },
  • index.js:160-184 (registration)
    Registration of the 'zaragoza-bizi-estimations' tool on the MCP server with name, description, schema, and handler.
    server.tool(
      "zaragoza-bizi-estimations",
      "Get the estimation of bikes and free slots in a Bizi station in Zaragoza in realtime",
      { station: z.number() },
      async ({ station }) => {
        const response = await fetch(
          `https://dndzgz.herokuapp.com/services/bizi/${station}`
        );
        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 Bizi station ${station}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'realtime' estimation, which is useful, but fails to cover critical aspects like rate limits, error handling, data freshness, or authentication requirements. For a tool that likely queries an external API, this omission leaves significant gaps in understanding its operational behavior.

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, well-structured sentence that efficiently conveys the core functionality without unnecessary words. It's front-loaded with the key action ('Get the estimation'), making it easy to parse quickly. Every part of the sentence adds value, achieving optimal conciseness.

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 query), lack of annotations, no output schema, and low schema description coverage, the description is incomplete. It doesn't explain the return format (e.g., JSON structure), error cases, or how to interpret 'bikes and free slots' data. This leaves the agent with insufficient information to handle the tool robustly in various scenarios.

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, so the description must compensate. It only implies a 'station' parameter without explaining what it represents (e.g., station ID, name, or how to obtain valid values). This lack of semantic detail makes it harder for an agent to use the tool correctly, as the parameter's meaning and format are unclear.

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 bikes and free slots in a Bizi station in Zaragoza in realtime.' It specifies the verb ('Get'), resource ('bikes and free slots'), and context ('Bizi station in Zaragoza'), making it easy to understand. However, it doesn't explicitly differentiate from its sibling 'zaragoza-bizi-stations', which might list stations rather than provide real-time availability estimates.

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 doesn't mention sibling tools like 'zaragoza-bizi-stations' (which might list stations) or other estimation tools (e.g., 'zaragoza-bus-estimations'), leaving the agent to infer usage based on context alone. This lack of explicit comparison reduces effectiveness in tool selection.

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