Skip to main content
Glama

swisstransport

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds meaningful context: 'derived from CF analytics-engine, no PII, just (pack, tool, count)' and 'Cached 5min-1h depending on window.' This discloses data provenance, privacy, and freshness without contradicting annotations.

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 front-loaded with a clear purpose, followed by a compact bulleted usage list and essential data-governance/caching caveats. Every sentence adds distinct information; no fluff or repetition.

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?

Despite no output schema, the description states the return contents ('top tools, top packs, and total call volume', 'just (pack, tool, count)'), and covers privacy, aggregation, and caching. For a single-optional-param read-only tool, this is fully complete.

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?

Schema coverage is 100% with a detailed enum description, so baseline is 3. The description adds value with 'Cached 5min-1h depending on window,' which is a parameter-dependent behavior not present in the schema, though it doesn't map specific windows to cache durations.

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?

The description opens with 'What other AI agents are calling on Pipeworx right now' and explicitly states it 'Returns the top tools, top packs, and total call volume over a recent window.' This is a specific verb+resource+scope that clearly differentiates it from siblings like ask_pipeworx or discover_tools.

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?

Provides explicit 'Useful for' list with three concrete scenarios (discovering hot data sources, confirming canonical tools, checking alignment with agent needs). It does not explicitly name alternatives or when-not-to-use, so it misses the full 5.

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

All swisstransport toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Most tools have distinct names and purposes, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) creates ambiguity as they serve overlapping needs with slight variations. Additionally, the transport tools (get_connections, get_stationboard, search_stations) are clearly distinct from the rest, but the overall set mixes domains, making it harder for an agent to know which tool to pick.

Naming Consistency3/5

All tool names use snake_case, but there is no consistent pattern: some start with verbs (get_, list_, search_, remember, forget), some with nouns (entity_profile, recent_changes, recent_alerts), and others with adjectives (ai_visibility_check, deep_research). This inconsistency, while not chaotic, makes the set less predictable.

Tool Count1/5

The server name 'swisstransport' implies a narrow Swiss transport focus, but with 34 tools, only 3 are transport-related. The count is vastly inappropriate for the suggested purpose. Even considering the actual broad domain (data query, prediction markets, memory), 34 tools is on the high side and likely overwhelming for any single server.

Completeness4/5

Inferring the domain from the tool descriptions, the set covers a wide range of capabilities: data query (ask_pipeworx, deep_research), entity comparison (compare_entities), prediction markets (polymarket_*), memory (remember/recall), subscriptions, and more. There are few obvious gaps given the scope; for example, broader financial data is accessible through ask_pipeworx. The transport subset is minimal but present.

Resources