worms-marine-taxa-mcp-server

Worms Get Classification

worms_get_classification

Read-onlyIdempotent

Retrieve root-to-tip classification and optional direct children for an AphiaID or canonical WoRMS LSID. resultOffset indexes lineage followed by fetched children; consume nextResultOffset with unchanged options and upstream offset before advancing page.nextOffset and resetting resultOffset to zero. Missing ranks remain unknown; child offset and filters are inactive without includeChildren. A full fetched 50-row child page has uncertain continuation and can lead to an empty page. The submitted ID keeps its own recorded lineage; a notice names its linked accepted ID, distinguishing an accepted alternative representation from its preferred ID.

Input Schema

Name	Required	Description
`offset`	No	One-based starting record, advancing by 50; default 1.
`aphiaId`	Yes	Positive safe-integer AphiaID, decimal string, or canonical urn:lsid:marinespecies.org:taxname:<AphiaID>; outputs remain numeric.
`extantOnly`	No	Extant children only; inactive without includeChildren.
`marineOnly`	No	Marine children only; inactive without includeChildren.
`resultOffset`	No	Zero-based position in lineage followed by fetched children; keep upstream offset unchanged until nextResultOffset is null.
`includeChildren`	No	Also fetch one page of direct children.

Output Schema

Name	Required	Description
`echo`	No	Effective options; child-only options inactive when includeChildren is false.
`page`	No	Children pagination only.
`error`	No	Present when the call failed. Absent on success.
`found`	No	Whether classification exists.
`ranks`	No	This segment of the root-to-tip lineage.
`notice`	No	Linked accepted/preferred-AphiaID and empty-children-page guidance, in that order.
`aphiaId`	No	Positive safe-integer AphiaID; obtain from worms_resolve_taxon.
`children`	No	One page of direct children when requested and retrieved.
`guidance`	No	Next step for absent classification.
`byteBudget`	No	Complete serialized response byte target.
`totalCount`	No	Known local sequence length before pagination.
`attribution`	No	WoRMS source attribution.
`statusError`	No	Failed taxonomic-status read; evidence is unaffected, but whether the AphiaID is its accepted name is unknown.
`resultOffset`	No	Zero-based starting position in the complete local sequence.
`budgetLimited`	No	Whether the byte budget ended this local page early.
`childrenError`	No	Optional children retrieval failure.
`oversizedItem`	No	One indivisible scientific item exceeds the target; retained intact with forward progress.
`requiredBytes`	No	Serialized paired-surface result bytes for an oversized item, excluding transport-added metadata.
`returnedCount`	No	Whole scientific items returned on this segment.
`nextResultOffset`	No	Next local position; null when consumed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses non-obvious behavior: missing ranks remain unknown, child filters are inactive without includeChildren, a full 50-row child page has uncertain continuation, and accepted-ID notices distinguish alternative representations. These are meaningful operational caveats for an open-world taxonomic lookup.

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?

The purpose is front-loaded and the dense pagination details are relevant, but the second and final sentences are long and syntactically complex. It earns its length through operational content, though clearer structure would improve readability.

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?

Given the available output schema, full parameter schema coverage, and safety annotations, the description is complete for correct invocation. It covers the tricky pagination lifecycle and edge cases that an agent would otherwise likely mishandle.

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%, so the baseline is 3. The description adds real value by explaining that resultOffset indexes lineage first and then fetched children, and by clarifying the interaction between nextResultOffset, page.nextOffset, and resetting resultOffset.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: retrieve root-to-tip classification and optional direct children for an AphiaID or LSID. It clearly distinguishes what data is returned, though it does not explicitly contrast itself with sibling tools such as worms_get_taxon or worms_get_synonyms.

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

Usage Guidelines2/5

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

The description explains pagination mechanics but does not state when to use this tool instead of alternatives like worms_get_taxon, worms_get_synonyms, or worms_get_traits. It also omits the prerequisite, present only in the schema, that the AphiaID should come from worms_resolve_taxon.

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

All worms-marine-taxa-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.