Pangaea

Recent

recent

Read-onlyIdempotent

Most recently published PANGAEA datasets (newest DOI registrations first).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Only datasets registered within the last N days (optional).
`size`	No	How many (default 20, max 50).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`total`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 16, 2026

removedOutput schema / properties / _shards

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

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```

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 / results

Added value: +{
+  "items": {
+    "properties": {
+      "authors": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "doi": {
+        "type": "string"
+      },
+      "id": {
+        "type": "number"
+      },
+      "registered": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "topics": {
+        "items": {
+          "type": [
+            "string",
+            null
+          ]
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      },
+      "year": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / timed_out
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / took

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

addedOutput schema / properties / total
```
Added value: +{
+  "type": "number"
+}
```

Changed2 schema fields changedJul 2, 2026
- addedInput schema / properties / days / description
```
Added value: +"Only datasets registered within the last N days (optional)."
```
- addedInput schema / properties / size / description
```
Added value: +"How many (default 20, max 50)."
```
First observedMay 25, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the sort order (newest first) and the time-based filtering concept, which is useful but minimal. No contradictions with annotations.

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 sentence, front-loaded with the core purpose and the ordering detail. It contains no fluff or redundancy, making it highly efficient for an agent to parse.

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?

Given that the tool has an output schema, complete parameter documentation, and annotations covering safety, the description is sufficient for a simple listing tool. It lacks explicit mention of pagination or output format, but the output schema handles that. It could mention the 'days' parameter more explicitly, but the overall context is adequate.

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 100% coverage with descriptions for both 'days' and 'size'. The tool description does not add extra meaning to these parameters beyond what the schema already provides. Since schema coverage is complete, the baseline of 3 applies.

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?

The description states the tool retrieves recently published PANGAEA datasets, ordered by newest DOI registrations. This clearly conveys the resource and purpose, and it distinguishes from siblings like search and dataset by focusing on recency and ordering. It lacks an explicit verb like 'list' or 'get', but the meaning is unambiguous.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as search or dataset. It implies it is for recent datasets but does not state exclusions or direct the agent to other tools for different needs. Given the sibling set includes search and dataset, explicit usage guidance would be valuable.

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.