Skip to main content
Glama

paleobiology-mcp-server: list geologic intervals

paleobiology_list_intervals
Read-onlyIdempotent

Look up the geologic time scale — eons, eras, periods, epochs, and ages with their absolute-age boundaries in millions of years (Ma) and nesting. This is the reference that grounds every temporal filter on the other tools and translates a named interval like "Late Cretaceous" to its 100.5–66.0 Ma boundaries (and back). Filter by a name substring, a Ma range (overlap match), and/or a level; call with no filters to browse the full scale. Browsing and every name on the bundled ICS international-scale snapshot are answered offline. A name the snapshot does not carry — the sub-stage and regional names that occurrence and collection rows report, such as "Late Maastrichtian" or "Lancian" — costs one PBDB lookup across its other time scales; the response names which source answered and which scale the interval belongs to.

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_list_intervals"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCase-insensitive substring of the interval name, e.g. "cretaceous" or "Jurassic". A name the bundled international scale does not carry is matched exactly against PBDB's other time scales.
levelNoRestrict to one rank of the international scale: eon, era, period, epoch, or age (finest). Browsing is bounded to that scale, so the sub-stage and regional ranks are not selectable here.
max_maNoOlder bound of an age window (Ma); intervals must overlap by more than a boundary point, including when only one bound is supplied. Must be at least min_ma when both are supplied; equal bounds include all intervals containing that point, including their boundaries.
min_maNoYounger bound of an age window (Ma); intervals must overlap by more than a boundary point, including when only one bound is supplied. Equal min_ma and max_ma select all intervals containing that point, including their boundaries.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when no interval matched the filters.
sourceNoWhich source answered: "bundled_ics" for the offline international-scale snapshot, "pbdb_upstream" for a name resolved live against PBDB's other time scales.
intervalsNoMatching geologic intervals, sorted oldest-first.
totalCountNoNumber of intervals matched by the filters.
snapshot_versionNoICS chart version and generation date of the bundled time scale, for citation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / max_ma / description
      Previous value: -"Older bound of an age window (Ma); intervals overlapping [min_ma, max_ma] match. When paired with min_ma it must be greater than or equal to it — equal bounds name a single point in time."New value: +"Older bound of an age window (Ma); intervals must overlap by more than a boundary point, including when only one bound is supplied. Must be at least min_ma when both are supplied; equal bounds include all intervals containing that point, including their boundaries."
    • changedInput schema / properties / min_ma / description
      Previous value: -"Younger bound of an age window (Ma); intervals overlapping [min_ma, max_ma] match."New value: +"Younger bound of an age window (Ma); intervals must overlap by more than a boundary point, including when only one bound is supplied. Equal min_ma and max_ma select all intervals containing that point, including their boundaries."
  2. Changed3 schema fields changed
    • changedInput schema / properties / max_ma / description
      Previous value: -"Older bound of an age window (Ma); intervals overlapping [min_ma, max_ma] match."New value: +"Older bound of an age window (Ma); intervals overlapping [min_ma, max_ma] match. When paired with min_ma it must be greater than or equal to it — equal bounds name a single point in time."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `interval_not_found`: A named interval filter matched nothing — neither the bundled international scale (after any level or Ma filters) nor a PBDB lookup across its other time scales. `interval_lookup_unavailable`: The name is outside the bundled international scale and the PBDB lookup that covers the other time scales could not be reached. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `interval_not_found`: A named interval filter matched nothing — neither the bundled international scale (after any level or Ma filters) nor a PBDB lookup across its other time scales. `interval_lookup_unavailable`: The name is outside the bundled international scale and the PBDB lookup that covers the other time scales could not be reached. `inverted_ma_range`: max_ma was smaller than min_ma — the age window is inverted. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "interval_not_found",
      -  "interval_lookup_unavailable"
      -]New value: +[
      +  "interval_not_found",
      +  "interval_lookup_unavailable",
      +  "inverted_ma_range"
      +]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already declare readOnly, idempotent, and openWorld, but the description adds substantive behavior beyond them: browsing and bundled ICS names are offline, unknown regional/sub-stage names cost one PBDB lookup, and the response identifies the source and scale. That is exactly the kind of context an agent needs for latency and reliability expectations.

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 description is front-loaded with the core purpose and is dense with relevant information, with no filler. It is somewhat long, but the length is justified by the offline/remote lookup caveat and parameter semantics.

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 that an output schema exists, the description does not need to explain return values, and it covers the important operational details: filtering modes, offline behavior, fallback lookups, and source attribution. Nothing critical for correct invocation appears to be missing.

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 all four parameters in detail. The description still adds useful semantics by clarifying substring versus exact matching for non-bundled names, overlap behavior for Ma ranges, and that level restricts browsing to the international-scale ranks only.

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 — looking up the geologic time scale with eon/era/period/epoch/age ranks, absolute-age boundaries, and nesting. It also distinguishes this reference tool from siblings by explaining that it grounds temporal filters used by the other tools.

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 clearly explains when to call with no filters (browse the full scale), when to filter by name substring, Ma range overlap, or level, and how to handle names outside the bundled snapshot. It also explains the offline versus PBDB lookup distinction, which is the key usage decision for this tool.

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.