Pangaea

Dataset By Doi

dataset_by_doi

Read-onlyIdempotent

Full metadata for one PANGAEA dataset by DOI (e.g. "10.1594/PANGAEA.921708" or the doi.org URL).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`doi`	Yes	PANGAEA DOI, e.g. "10.1594/PANGAEA.921708".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`doi`	No
`url`	No
`year`	No
`title`	No
`topics`	No
`authors`	No
`registered`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 16, 2026

removedOutput schema / properties / _shards

Removed value: -{
-  "type": "object"
-}

addedOutput schema / properties / authors

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / doi
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / hits

Removed value: -{
-  "properties": {
-    "hits": {
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "max_score": {
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "total": {
-      "type": "object"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / id
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / registered
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / timed_out
```
Removed value: -{
-  "type": "boolean"
-}
```
addedOutput schema / properties / title
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / took

Removed value: -{
-  "type": "number"
-}

addedOutput schema / properties / topics

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / year
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedJul 2, 2026
- addedInput schema / properties / doi / description
```
Added value: +"PANGAEA DOI, e.g. \"10.1594/PANGAEA.921708\"."
```
First observedMay 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description goes beyond those by clarifying that the tool accepts either a raw DOI or a doi.org URL, and that it returns full metadata for exactly one dataset. These are useful behavioral details not present in the annotations. No contradictions exist.

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?

The description is a single well-structured sentence that front-loads the core purpose, includes a concrete example, and notes an alternate accepted input format. Every part earns its place with no filler or redundancy.

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?

For a simple single-parameter read-only tool, the description, schema, and annotations together provide everything needed to invoke it correctly. The output schema exists, so the description does not need to explain return values. There are no missing prerequisites, permissions, or edge-case behaviors that an agent would need to know.

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?

The input schema already fully describes the 'doi' parameter, giving 100% schema coverage, so the baseline is 3. The description adds value by explicitly stating that the doi.org URL form is also accepted, which is not mentioned in the schema. This clarification helps agents format the parameter correctly.

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 clearly states that this tool returns full metadata for one PANGAEA dataset identified by DOI, which is a specific verb-resource pairing. It distinguishes itself from broader search or generic dataset tools by emphasizing 'one' dataset and DOI-based lookup. The supplied examples make the expected input format immediately obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the right usage context—when a specific PANGAEA DOI is known and full metadata is needed—but it does not explicitly state when to prefer this tool over alternatives like 'search' or 'dataset'. There is no direct comparison to sibling tools or exclusionary guidance, so the guidance is more implied than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pangaea tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.