Skip to main content
Glama

Macrostrat Stratigraphic Column Search

macrostrat.geology.columns_search
Read-onlyIdempotent

Search worldwide stratigraphic columns (a summary of the rock units at one location) by point location (lat/lng), stratigraphic name, chronostratigraphic time interval, lithology, or geologic age (Ma). Returns column IDs, names, coordinates, area, and thickness — use the returned col_id with macrostrat.units_search or macrostrat.fossils_search. Data: macrostrat.org/api/v2, no auth required, CC BY 4.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoNumerical age in millions of years before present (Ma)
latNoDecimal degree latitude (WGS84) — must be supplied together with lng
lngNoDecimal degree longitude (WGS84) — must be supplied together with lat
lithNoLithology name to filter by, e.g. "sandstone" or "shale"
age_topNoYounger bound of an age range in Ma — must be used with age_bottom
adjacentsNoIf lat+lng given, also return columns touching the same polygon (default false)
age_bottomNoOlder bound of an age range in Ma — must be used with age_top
strat_nameNoFuzzy stratigraphic name to match, e.g. "mancos" or "jordan"
interval_nameNoChronostratigraphic time interval name, e.g. "Permian" or "Cretaceous"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already cover the safety profile (read-only, non-destructive, idempotent). The description adds valuable context beyond them: the underlying API source, that no auth is required, the CC BY 4.0 license, worldwide scope, and the specific fields returned. This goes beyond simple annotation repetition and helps an agent understand integration implications.

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?

Three carefully scoped sentences: the first states action and search dimensions, the second states return fields and downstream tool usage, and the third covers source and licensing. Every sentence earns its place, with no redundant phrasing or filler.

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 to describe return values, the description appropriately focuses on selection guidance and invocation context. It covers data provenance, licensing, no-auth access, filter options, and the correct follow-up tools, so an agent has everything needed to invoke the tool correctly.

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?

The input schema has thorough, descriptive entries for all nine parameters, achieving 100% coverage. The description only paraphrases the filter categories (lat/lng, stratigraphic name, time interval, lithology, Ma) without adding syntax, formats, or operation rules. This matches the baseline-3 expectation when schema does the heavy lifting.

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 opens with a specific verb ('Search'), identifies the resource ('worldwide stratigraphic columns'), defines what a stratigraphic column is, and enumerates the distinct filter dimensions (point location, stratigraphic name, time interval, lithology, geologic age). It also clarifies its role among siblings by noting the returned col_id feeds into macrostrat.units_search or macrostrat.fossils_search.

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?

It clearly states what this tool searches and lists the viable filter inputs, while explicitly directing agents to downstream tools for unit or fossil-level queries. It lacks explicit 'do not use this when...' language, but the positive usage context is strong and the follow-up instruction effectively routes agents away from overextending 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.