Skip to main content
Glama

Worms

by io.github.pipeworx-io

Search Species

search_species
Read-onlyIdempotent

Resolve a marine species or genus name to its WoRMS AphiaID, accepted name, authority, status (accepted/unaccepted), rank, and high-level classification (kingdom/family/genus). WoRMS is the authoritative world register of marine species. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesScientific name to look up, e.g. "Orcinus orca" or "Octopus".
fuzzyNoFuzzy/like matching (LIKE substring). Default false (exact).
marine_onlyNoRestrict to marine taxa. Default true.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds that the tool is keyless and relies on WoRMS as authoritative source, which is useful context beyond 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?

Two sentences that are front-loaded with the core action and output. Every sentence adds value without redundancy.

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?

Given no output schema, the description clearly enumerates the return fields (AphiaID, accepted name, authority, status, rank, classification). It also specifies keyless access. Could mention pagination or multiple match handling, but overall sufficient for a lookup tool.

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?

Input schema has 100% description coverage for all 3 parameters. The description does not add significant new meaning beyond what the schema provides, but it does list the return fields (AphiaID, accepted name, etc.) which are not parameters.

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 clearly states it resolves a marine species or genus name to WoRMS AphiaID and taxonomic details. It differentiates from siblings like get_common_names or get_classification by specifying the source (WoRMS) and the exact outputs.

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

Usage Guidelines3/5

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

The description implies usage for marine species lookups and notes it's keyless, but does not explicitly state when to use over siblings or when not to use (e.g., if the name is not marine). No alternative tools are mentioned.

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

All Worms 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.6/5.0
Disambiguation2/5

Several tools have functionally overlapping purposes, most notably ask_pipeworx and ask_pipeworx_beta, which currently behave identically. The many prediction-market tools are each distinct but still leave boundaries that require careful reading, and the query/research tools (ask_pipeworx, deep_research, potentially validate_claim) have an ease of being confused. Fine verbal descriptions reduce but do not eliminate the ambiguity for an agent.

Naming Consistency3/5

All names are lowercase snake_case and many follow a verb_noun pattern, such as resolve_entity, get_classification, and list_subscriptions. However, the set is inconsistent overall: it mixes single verbs (remember, forget, subscribe), noun-style names (entity_profile, recent_alerts), and several prefixed families (pipeworx_*, polymarket_*). It's readable but not a coherent, uniformly applied convention throughout.

Tool Count2/5

34 tools in one server is well beyond the generally well-scoped 3–15 range. The server appears to bundle several unrelated domains together—WoRMS taxonomy, Pipeworx data research, Polymarket analysis, memory utilities, and subscriptions—creating avoidable cognitive load and making selection more difficult. Splitting into targeted servers would greatly improve the interface.

Completeness2/5

The server is named 'Worms' and includes a WoRMS taxonomy subdomain, but that subdomain only supports searching, classification, and common names—the rest of the marine taxonomy surface is missing (e.g., direct AphiaID record lookup, distributions, synonyms, hierarchical children). The remainder of the tools serve an entirely different data-research purpose, so the server is incomplete relative to its name AND the bundled extra domains add confusion rather than a coherent cohesive coverage.

Resources