Skip to main content
Glama

Swiss shared-mobility providers

list_shared_mobility_providers
Read-only

List bike, e-bike, scooter, moped, car and cargo-bike sharing providers from sharedmobility.ch; filter by name or vehicle type to find provider IDs and app links.

Instructions

All bike/e-bike/e-scooter/moped/car/cargo-bike sharing providers in the sharedmobility.ch national aggregator: provider_id, name, vehicle types, website and Android/iOS app links. Filter by name substring (query: 'publibike') or vehicle_type ('car'). Provider names match the 'provider' field of get_shared_vehicles_nearby.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoSubstring of provider name or id, e.g. 'mobility', 'voi'
vehicle_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and openness, and the description adds useful context: it is a national aggregator, it lists exactly what fields come back (provider_id, name, vehicle types, website, app links), which matters since there is no output schema. It does not mention result-size behavior or pagination.

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 dense, front-loaded sentence followed by a short filtering/cross-reference sentence; every clause carries information. The run-on enumeration of vehicle types is slightly heavy but not wasteful.

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

Completeness4/5

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

For a read-only list tool with no output schema, the description supplies the return fields and the join key to a sibling, which is the key missing piece. The only gap is the undocumented limit parameter and the enum-label mismatch.

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?

Schema coverage is 33% (only query is documented), and the description compensates by explaining query as a name substring with an example and vehicle_type as the vehicle filter. However, the limit parameter (default 100, max 200) is never mentioned, and the description's labels ('e-scooter', 'cargo-bike') do not match the enum values ('scooter', 'cargo_bike'), which is a real ambiguity for the agent.

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?

States a specific verb and resource ('All bike/e-bike/e-scooter/moped/car/cargo-bike sharing providers') plus the source ('sharedmobility.ch national aggregator'), and enumerates the returned fields. It also names the sibling it relates to (get_shared_vehicles_nearby), so an agent can distinguish it from neighborhood-vehicle lookups.

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?

Gives concrete filtering conditions with examples ('query: publibike', vehicle_type: 'car') and explains the relationship to get_shared_vehicles_nearby via the matching 'provider' field. It stops short of explicit when-not-to-use guidance, but the usage context is clear.

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

Deploy Server

Other Tools