Skip to main content
Glama

paleobiology-mcp-server: get bibliographic references

paleobiology_get_references
Read-onlyIdempotent

Resolve PBDB reference_no values — the source publication on every paleobiology_search_occurrences and paleobiology_search_collections row — to full citations with authors, year, title, publication, volume, pages, and DOI. Pass the ids from a page of rows in one call: the first 500 distinct ids are resolved and any beyond that come back in remaining_reference_nos for a follow-up call. Ids PBDB has no reference for are listed in not_found. Results keep the order the ids were given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference_nos": "<reference_nos>"
    },
    "name": "paleobiology_get_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
reference_nosYesPBDB reference ids to resolve, from occurrence or collection rows. Repeats are resolved once. The first 500 distinct ids are resolved per call; any remaining ids are returned for continuation.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when some ids had no PBDB reference, or when more ids remain than one call resolves.
not_foundNoRequested ids PBDB has no reference for. Empty when every id resolved.
referencesNoThe references PBDB has, in the order their ids were given.
attributionNoCC-BY data attribution for the Paleobiology Database.
remaining_reference_nosNoDistinct ids past the first 500, not resolved by this call — pass them as reference_nos to resolve the rest. Present only when the input held more than 500 distinct ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / reference_nos / description
      Previous value: -"PBDB reference ids to resolve, from the reference_no field of paleobiology_search_occurrences or paleobiology_search_collections rows. Repeats are resolved once. Up to 500 accepted; the first 25 distinct ids are resolved per call."New value: +"PBDB reference ids to resolve, from occurrence or collection rows. Repeats are resolved once. The first 500 distinct ids are resolved per call; any remaining ids are returned for continuation."
    • removedInput schema / properties / reference_nos / maxItems
      Removed value: -500
    • changedOutput schema / properties / references / items / properties / citation / description
      Previous value: -"Full citation as PBDB formats it, plain text, relayed as entered (authors, year, title, publication, volume, pages)."New value: +"Full PBDB citation converted from HTML to plain text (authors, year, title, publication, volume, pages)."
    • changedOutput schema / properties / remaining_reference_nos / description
      Previous value: -"Distinct ids past the first 25, not resolved by this call — pass them as reference_nos to resolve the rest. Present only when the input held more than 25 distinct ids."New value: +"Distinct ids past the first 500, not resolved by this call — pass them as reference_nos to resolve the rest. Present only when the input held more than 500 distinct ids."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: the first 500 distinct ids are resolved, extra ids return in remaining_reference_nos, unresolved ids appear in not_found, and output order follows input order. These are critical operational details for correct invocation and follow-up.

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?

The description is dense but front-loaded: purpose first, then batching behavior, failure handling, and ordering. Every sentence carries actionable information without 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?

Given a single fully documented parameter, an output schema, and read-only/idempotent/open-world annotations, the description covers the important remaining behavior: batching limits, continuation, unresolved ids, and result order.

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?

The schema already fully documents reference_nos, including repeat handling and the 500-id cap. The description adds conceptual context by identifying these as source-publication ids from occurrence and collection rows and by reinforcing page-based batching.

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?

States a specific verb and resource: resolving PBDB reference_no values into full citations. It explicitly ties reference numbers to source publications on paleobiology_search_occurrences and paleobiology_search_collections rows, making its role distinct from sibling search tools.

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?

Explains the key usage pattern: pass ids from a page of rows in one call, with a 500-id resolution limit and remaining_reference_nos for follow-up. It does not name an alternative reference-lookup tool, but no clear sibling alternative exists and the batching guidance is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.