Skip to main content
Glama

Wikipathways

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.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark readOnlyHint=true, destructiveHint=false, and idempotentHint=true. Description goes beyond by revealing data source (CF analytics-engine), privacy (no PII), aggregation method, and caching duration (5min-1h). No contradictions.

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?

Three tightly written sentences with no redundancy. Front-loaded with core purpose, followed by use cases, then technical details. Every sentence adds value.

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 tool with no output schema, the description adequately describes return format ('top tools, top packs, total call volume'). It also covers caching, privacy, and data source, making the tool's behavior fully understandable.

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 one parameter (window). The description adds semantic value by explaining that shorter windows surface what's hot now while longer windows show steady-state demand, which aids parameter selection beyond the enum values.

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?

Description clearly states the tool returns trending data: 'top tools, top packs, and total call volume' over a window. This verb+resource combination ('what other AI agents are calling') is specific and distinct from sibling tools like discover_tools or search_within.

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?

Explicitly lists three concrete use cases (discovering hot data sources, confirming canonical tool, checking alignment). While it doesn't state when not to use it or name alternatives, the examples provide clear guidance on appropriate contexts.

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

All Wikipathways 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

B3.3/5.0
Disambiguation1/5

The tool set is severely mismatched: only 3 of 34 tools (get_pathway, list_pathways, search_pathways) relate to WikiPathways while the rest form overlapping Pipeworx/Polymarket families (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded; multiple polymarket_* tools) with unclear boundaries and overlapping purposes.

Naming Consistency2/5

Naming conventions are highly inconsistent: product-specific names (pipeworx_feedback, pipeworx_trending), generic memory verbs (remember, recall, forget), and mixed snake_case patterns with no unifying verb_noun structure. The names do not reflect the WikiPathways domain at all.

Tool Count1/5

34 tools is far too many for a WikiPathways server, which only needs a handful of pathway-related operations. Nearly all tools belong to unrelated domains (SEC, FDA, Polymarket, npm, etc.), making the set feel bloated and unfocused.

Completeness1/5

For the stated WikiPathways purpose, only get, list, and search are present—no create, update, or delete operations—leaving obvious lifecycle gaps. The extensive non-WikiPathways tools do not contribute to the server's apparent domain coverage and create dead ends for agents expecting pathway management.

Resources