Skip to main content
Glama

Pangaea Dataset

pangaea_dataset
Read-onlyIdempotent

Full metadata for one PANGAEA dataset by its numeric ID (e.g. 921708).

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": {
      "id": 823127
    },
    "name": "pangaea_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPANGAEA dataset ID, e.g. 921708.

Output Schema

NameRequiredDescriptionDefault
idNo
doiNo
urlNo
yearNo
titleNo
topicsNo
authorsNo
registeredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds that it returns full metadata for one dataset, but does not discuss error handling, rate limits, or result size; with an output schema present, this is adequate but not rich.

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?

A single front-loaded sentence with no filler. It communicates the core operation and key constraint efficiently.

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 single-parameter lookup with annotations and an output schema, the description is sufficient. It could mention invalid-ID behavior, but nothing essential for selecting or invoking the tool is missing.

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 sole id parameter is fully documented in the schema, including an example. The description repeats that it is a numeric ID but adds no validation, formatting, or lookup details beyond what the schema provides.

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 action (retrieve full metadata) and resource (one PANGAEA dataset), and identifies the lookup key as a numeric ID, which helps distinguish it from DOI-based lookup siblings.

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?

The numeric-ID framing gives clear context for when this tool applies and contrasts implicitly with dataset_by_doi. It does not explicitly name alternatives or state when not to use it, so it lacks full routing guidance.

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.