Skip to main content
Glama

Pangaea Search

pangaea_search
Read-onlyIdempotent

Full-text search of PANGAEA earth/environmental science datasets (oceanography, climate, geology, biology, paleo). Returns dataset title, DOI, authors, year, and topics. Use for questions like "ocean temperature datasets", "Arctic sea ice cores", "CO2 flux measurements".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOffset for pagination (default 0).
sizeNoResults to return (default 20, max 50).
queryNoFree-text search, e.g. "ocean temperature", "Arctic sea ice". Omit to browse everything.

Output Schema

NameRequiredDescriptionDefault
fromNo
countNo
totalNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is fully covered without description help. The description adds only the returned field set (title, DOI, authors, year, topics) and the full-text scope, and the former is largely restated by the existing output schema. No mention of result caps beyond the schema or of ranking/recall behavior.

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?

Two sentences, front-loaded with the core capability before the usage examples, with no filler. The quoted example queries earn their place by anchoring the free-text behavior, though three of them border on redundant with the parenthetical domain list.

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 read-only search tool with rich annotations, a fully documented three-parameter schema, and an output schema, the description covers what, over what corpus, and typical query shapes. Nothing an agent needs to invoke it correctly is missing, though the sibling routing gap keeps it from being fully complete.

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 description coverage is 100%, with from, size, and query each documented including defaults and the max of 50, so the structured data already does the heavy lifting. The description adds no syntax guidance (phrase quoting, boolean operators, fielded search) that would go beyond "free-text search".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: full-text search over PANGAEA earth/environmental science datasets, with an explicit enumeration of subject domains (oceanography, climate, geology, biology, paleo). It does not distinguish itself from near-name siblings such as pangaea_dataset, pangaea_facets, or pangaea_recent, so the agent must infer the boundary.

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?

"Use for questions like ..." supplies three concrete query archetypes, giving clear positive guidance on when to reach for this tool. It never states when NOT to use it or names an alternative such as pangaea_dataset for a known-DOI lookup, so the routing decision against siblings is left implicit.

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.