Skip to main content
Glama
Sign In

Citybikes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Network

get_network
Read-onlyIdempotent

Check live bike availability at stations in a specific network (e.g., "citi-bike-nyc"). Returns station locations, available bikes, and empty slots.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "citi-bike-nyc"
    },
    "name": "get_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNetwork id (e.g. "citi-bike-nyc", "velib" for Paris, "nextbike-berlin")

Output Schema

NameRequiredDescriptionDefault
idYesNetwork identifier
cityYesCity where network operates
nameYesNetwork name
countryYesCountry where network operates
stationsYesArray of stations in network
station_countYesTotal number of stations in network

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "city": {
+      "description": "City where network operates",
+      "type": "string"
+    },
+    "country": {
+      "description": "Country where network operates",
+      "type": "string"
+    },
+    "id": {
+      "description": "Network identifier",
+      "type": "string"
+    },
+    "name": {
+      "description": "Network name",
+      "type": "string"
+    },
+    "station_count": {
+      "description": "Total number of stations in network",
+      "type": "integer"
+    },
+    "stations": {
+      "description": "Array of stations in network",
+      "items": {
+        "properties": {
+          "empty_slots": {
+            "description": "Number of empty docking slots",
+            "type": "integer"
+          },
+          "free_bikes": {
+            "description": "Number of available bikes",
+            "type": "integer"
+          },
+          "id": {
+            "description": "Station identifier",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Station latitude",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Station longitude",
+            "type": "number"
+          },
+          "name": {
+            "description": "Station name",
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "Last update timestamp",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "free_bikes",
+          "empty_slots",
+          "latitude",
+          "longitude",
+          "timestamp"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "city",
+    "country",
+    "station_count",
+    "stations"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "citi-bike-nyc"
+  },
+  {
+    "id": "velib"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds useful behavioral context by specifying what is returned (station locations, available bikes, empty slots), which goes beyond the annotation flags without contradicting them.

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, focused sentence that states the action and outcome. No filler or repetition, making it appropriately concise and front-loaded.

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

Completeness5/5

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

For a simple one-parameter tool with rich annotations and an output schema, the description fully covers the purpose and return contents. No critical information is missing, and the tool's behavior is sufficiently clear for an agent to use it correctly.

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?

The schema already provides full parameter documentation with examples and coverage at 100%. The description only echoes the same example ("citi-bike-nyc") without adding additional meaning, so it meets the baseline but adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool checks live bike availability at stations for a specific network, with a concrete example ("citi-bike-nyc"). This distinguishes it from sibling tools like list_networks or search_networks, which manage networks rather than station-level availability.

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

Usage Guidelines4/5

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

The description implies the tool is for when you have a specific network id in mind, saying "in a specific network." It does not explicitly mention alternatives or when not to use it, but the context is clear enough for a simple lookup tool.

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

All Citybikes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources