worms-marine-taxa-mcp-server

Worms Crosswalk Id

worms_crosswalk_id

Read-onlyIdempotent

Crosswalk an AphiaID from worms_resolve_taxon to one or all nine external identifier systems, or reverse an externalId with required type to a full taxon record. Supply exactly one selector. Forward resultOffset indexes whole identifiers across types in requested order; resume nextResultOffset with unchanged selectors. typeTotals distinguishes successful absence from IDs on another segment; failed types remain separate. IDs stay opaque, including leading zeros and LSIDs. No IDs cannot establish taxon absence; IUCN identifiers are not threat categories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "worms_crosswalk_id"
  }
}

Input Schema

Name	Required	Description
`type`	No	Required for reverse; omit forward to query all nine types. Codes ignore case and surrounding whitespace. See worms_list_reference external_id_types.
`aphiaId`	No	Forward numeric AphiaID, decimal string, or canonical WoRMS LSID; mutually exclusive with externalId.
`externalId`	No	Reverse selector; opaque identifier up to 512 characters; blank omitted.
`resultOffset`	No	Zero-based forward identifier position across types in requested order; repeat unchanged selectors. Inactive for reverse lookup.

Output Schema

Name	Required	Description
`ids`	No	This segment of answered types; consult typeTotals to distinguish empty evidence from IDs on another segment.
`echo`	No	Effective crosswalk selectors.
`type`	No	Explicitly selected identifier system.
`error`	No	Present when the call failed. Absent on success.
`found`	No	Reverse match state; null in forward mode.
`notice`	No	Partial-outage retry guidance.
`record`	No	Reverse matched record only.
`aphiaId`	No	Supplied or matched taxon ID; null for reverse misses.
`guidance`	No	Guidance when no identifiers or reverse match are found.
`direction`	No	Selected crosswalk direction.
`byteBudget`	No	Complete serialized response byte target.
`externalId`	No	Opaque reverse identifier, preserved as text.
`totalCount`	No	Known local sequence length before pagination.
`typeTotals`	No	Answered types only; zero means successful absence; failed types are omitted.
`attribution`	No	WoRMS source attribution.
`failedTypes`	No	Failed types in fixed vocabulary order.
`resultOffset`	No	Zero-based starting position in the complete local sequence.
`budgetLimited`	No	Whether the byte budget ended this local page early.
`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

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, but the description adds substantial behavioral context: identifiers stay opaque (including leading zeros and LSIDs), no IDs cannot establish taxon absence, IUCN identifiers are not threat categories, and typeTotals separates absence from another-segment IDs. These are meaningful operational caveats beyond the annotations.

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 every clause carries useful information. It is somewhat dense and semicolon-packed, but there is no obvious filler 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?

With an output schema present, the description need not explain return values. It covers the key gaps: selector rules, reverse/forward behavior, pagination resumption, opaque ID handling, and absence semantics.

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 schema already documents the four parameters well. The description still adds value by clarifying selector exclusivity, forward-vs-reverse type behavior, and the meaning of resultOffset as a position across identifier types.

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 states a specific verb and resource: crosswalk an AphiaID to/from external identifier systems. It also distinguishes the tool from worms_resolve_taxon and worms_list_reference, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says to supply exactly one selector, that type is required for reverse lookup and omitted for forward lookup across all nine types, and that AphiaID comes from worms_resolve_taxon. It also gives pagination guidance for resultOffset and nextResultOffset.

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.