get_pathwayGet metadata and a viewer link for one WikiPathways pathway by its WikiPathways id (e.g. "WP554"). Returns name, species, revision, and a human-viewable diagram URL. Keyless.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | A WikiPathways id like "WP554". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. The description adds that it returns specific metadata and a viewer URL, which is useful but does not reveal significant additional behavioral traits beyond what annotations cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences that front-load the main action and output. No wasted words; each sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter retrieval tool with no output schema, the description adequately covers return fields. It is complete enough given the tool's simplicity and annotation richness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents the 'id' parameter. The description adds an example format ('WP554') but does not significantly extend meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves metadata and a viewer link for a single WikiPathways pathway by ID, listing returned fields (name, species, revision, diagram URL). It is specific but does not explicitly distinguish from sibling tools like list_pathways or search_pathways.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for fetching a known pathway by ID, mentioning 'Keyless' for authentication context, but lacks explicit guidance on when to use this vs alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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.