Skip to main content
Glama

paleobiology-mcp-server: search fossil collections

paleobiology_search_collections
Read-onlyIdempotent

Find fossil collections (localities) by area and geologic time — "what has been dug up here, and from what rock." Each locality returns its location, age (named interval and Ma), formation and strata, lithology, depositional environment, and the count of co-occurring fossils. Filter by a clade-inclusive base_name (or base_id, the same clade by resolved taxon id), a named interval or max_ma/min_ma range, a lng/lat bounding box, a formation or lithology name, and/or an environment. Results page inline via limit/offset (the response discloses when more remain). Take a collection_no from a row and pass it — or the same bbox+interval — to paleobiology_search_occurrences to see the actual fauna found together.

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": "paleobiology_search_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum localities to return per page, up to 10000, subject to PBDB_MAX_OCCURRENCES. Every fetched row is returned; the notice discloses a lower configured cap.
latmaxNoNorthern edge of the bounding box, decimal degrees (−90…90). Valid on its own — a lone latitude edge filters as a half-plane.
latminNoSouthern edge of the bounding box, decimal degrees (−90…90). Valid on its own — a lone latitude edge filters as a half-plane.
lngmaxNoEastern edge of the bounding box, decimal degrees (−180…180). Longitude is a closed pair — supply lngmin with it or neither.
lngminNoWestern edge of the bounding box, decimal degrees (−180…180). Longitude is a closed pair — supply lngmax with it or neither.
max_maNoOlder age bound in millions of years ago. When paired with min_ma it must be strictly greater — max_ma is the deeper-time end of the window.
min_maNoYounger age bound in millions of years ago. When paired with max_ma it must be strictly smaller — min_ma is the nearer-to-present end of the window.
offsetNoNumber of localities to skip — page with limit by advancing offset.
base_idNoClade-inclusive taxon filter by PBDB taxon id — the accepted_no from paleobiology_get_taxon or an occurrence row. Same semantics as base_name, but unambiguous where a name is not (homonyms, synonyms, unresolved spellings). Supply this or base_name, never both.
countryNoPBDB country/continent codes, comma-separated; ! excludes a list and ^ subtracts a code, e.g. NOA,^US.
intervalNoNamed geologic interval bounding the age, e.g. "Maastrichtian". Alternative to max_ma/min_ma.
base_nameNoClade-inclusive taxon filter — localities yielding this taxon or its descendants, e.g. "Dinosauria". Supply this or base_id, never both.
formationNoStored geologic formation name or PBDB list/wildcard expression, e.g. "Hell Creek"; passed unchanged, without stripping Formation, Group, or Member.
lithologyNoLithology (rock type) to filter by, e.g. "sandstone".
environmentNoDepositional environment: "marine", "terrestrial", or "freshwater" (lacustrine + fluvial). Omit for all.

Output Schema

NameRequiredDescriptionDefault
capNoThe per-page limit that was applied (set when truncated).
errorNoPresent when the call failed. Absent on success.
shownNoNumber of localities returned in this page (set when truncated).
noticeNoApplied filters and guidance when no locality matched, localities remain past this page, offset ran past the match set, or PBDB ignored a filter value.
truncatedNoTrue when localities remain past this page — advance offset for more.
totalCountNoTotal localities matching the filters upstream, across all pages.
attributionNoCC-BY data attribution for the Paleobiology Database.
collectionsNoMatching localities for this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / base_id / description
      Previous value: -"Clade-inclusive taxon filter by PBDB taxon id — the taxon_no from paleobiology_get_taxon, or accepted_no on an occurrence row. Same semantics as base_name, but unambiguous where a name is not (homonyms, synonyms, unresolved spellings). Supply this or base_name, never both."New value: +"Clade-inclusive taxon filter by PBDB taxon id — the accepted_no from paleobiology_get_taxon or an occurrence row. Same semantics as base_name, but unambiguous where a name is not (homonyms, synonyms, unresolved spellings). Supply this or base_name, never both."
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "PBDB country/continent codes, comma-separated; ! excludes a list and ^ subtracts a code, e.g. NOA,^US.",
      +  "pattern": "^[!^]?(?:[A-Z]{2}|NOA|SOA|EUR|ASI|AFR|AUS|ATA|OCE|IOC)(?:,\\^?(?:[A-Z]{2}|NOA|SOA|EUR|ASI|AFR|AUS|ATA|OCE|IOC))*$",
      +  "type": "string"
      +}
    • changedInput schema / properties / formation / description
      Previous value: -"Geologic formation name to filter by, e.g. \"Hell Creek\"."New value: +"Stored geologic formation name or PBDB list/wildcard expression, e.g. \"Hell Creek\"; passed unchanged, without stripping Formation, Group, or Member."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum localities to return per page. Up to 500 are pulled per call; a larger value is served at 500, and the paging notice names that cap when more matches remain. A page can show fewer rows than it pulled when more would exceed the inline response size — the notice then names the offset that continues."New value: +"Maximum localities to return per page, up to 10000, subject to PBDB_MAX_OCCURRENCES. Every fetched row is returned; the notice discloses a lower configured cap."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no locality matched, when localities remain past this page or it was cut to fit the inline response size (naming the offset that reaches the next one), when offset ran past the end of the match set, or when a filter value was not recognized and ignored."New value: +"Applied filters and guidance when no locality matched, localities remain past this page, offset ran past the match set, or PBDB ignored a filter value."
  2. Changed6 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum localities to return per page (1–500)."New value: +"Maximum localities to return per page. Up to 500 are pulled per call; a larger value is served at 500, and the paging notice names that cap when more matches remain. A page can show fewer rows than it pulled when more would exceed the inline response size — the notice then names the offset that continues."
    • changedInput schema / properties / limit / maximum
      Previous value: -500New value: +10000
    • changedOutput schema / properties / collections / items / properties / reference_no / description
      Previous value: -"PBDB bibliographic reference id for provenance."New value: +"PBDB bibliographic reference id — the publication this collection was entered from. Resolve it to a full citation with paleobiology_get_references."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `missing_filter`: The call carried only pagination fields — no taxon, time, place, formation, lithology, or environment filter. `conflicting_taxon_filter`: Both base_name and base_id were supplied — PBDB accepts only one clade selector. `incomplete_bbox`: Exactly one of lngmin/lngmax was supplied — a longitude box needs both edges. `inverted_ma_range`: min_ma was greater than or equal to max_ma — the age window is inverted or empty. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `missing_filter`: The call carried only pagination fields — no taxon, time, place, formation, lithology, or environment filter. `conflicting_taxon_filter`: Both base_name and base_id were supplied — PBDB accepts only one clade selector. `incomplete_bbox`: Exactly one of lngmin/lngmax was supplied — a longitude box needs both edges. `inverted_ma_range`: min_ma was greater than or equal to max_ma — the age window is inverted or empty. `pbdb_invalid_parameter`: PBDB refused a filter value it could not use, such as an unknown interval or lithology name — the message quotes its reason. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "missing_filter",
      -  "conflicting_taxon_filter",
      -  "incomplete_bbox",
      -  "inverted_ma_range"
      -]New value: +[
      +  "missing_filter",
      +  "conflicting_taxon_filter",
      +  "incomplete_bbox",
      +  "inverted_ma_range",
      +  "pbdb_invalid_parameter"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no locality matched, when localities remain past this page, or when a filter value was not recognized and ignored."New value: +"Guidance when no locality matched, when localities remain past this page or it was cut to fit the inline response size (naming the offset that reaches the next one), when offset ran past the end of the match set, or when a filter value was not recognized and ignored."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds genuinely new behavior: results page inline via limit/offset and "the response discloses when more remain." It does not discuss the configured cap (PBDB_MAX_OCCURRENCES) or any timeout/rate-limit behavior, so it stops short of a 5.

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?

Front-loaded with the purpose and a scannable gloss before the filter enumeration. However, the middle sentence is a long run-on that duplicates schema-documented filters, and the return-field enumeration is partly redundant given an output schema exists.

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?

For a 15-parameter, fully-optional filter tool with an output schema, the description covers purpose, filter surface, pagination, and the sibling handoff. Nothing an agent needs to call it correctly appears missing; only the return-value enumeration is surplus.

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?

Schema coverage is 100%, so baseline is 3; the description's filter list (base_name/base_id, interval or min_ma/max_ma, bbox, formation, lithology, environment) largely restates what the schema already documents in more precise terms. It only adds the either/or relationship framing for base_name vs base_id and interval vs Ma range, which the schema already states.

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 ("Find fossil collections (localities)") plus two scoping dimensions (area, geologic time) and a memorable framing of what a row contains. It is clearly distinct from paleobiology_search_occurrences, which the description names as the fauna-level counterpart.

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?

Explicitly routes the agent: take a collection_no from a row (or the same bbox+interval) and pass it to paleobiology_search_occurrences "to see the actual fauna found together" — a real when-to-use-which rule. It also states the filter combinations up front so the agent knows what a query can look like.

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.