Skip to main content
Glama

Pangaea

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

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".

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
fromNo
countNo
totalNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / _shards
      Removed value: -{
-  "description": "Shard information",
-  "properties": {
-    "failed": {
-      "type": "number"
-    },
-    "skipped": {
-      "type": "number"
-    },
-    "successful": {
-      "type": "number"
-    },
-    "total": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / from
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / hits
      Removed value: -{
-  "description": "Search hits container",
-  "properties": {
-    "hits": {
-      "description": "Array of matching documents",
-      "items": {
-        "properties": {
-          "_id": {
-            "type": "string"
-          },
-          "_index": {
-            "type": "string"
-          },
-          "_score": {
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "_source": {
-            "description": "Document source",
-            "type": "object"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "max_score": {
-      "description": "Maximum relevance score",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "total": {
-      "properties": {
-        "relation": {
-          "type": "string"
-        },
-        "value": {
-          "description": "Total number of matching documents",
-          "type": "number"
-        }
-      },
-      "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",
+          "null"
+        ]
+      },
+      "title": {
+        "type": "string"
+      },
+      "topics": {
+        "items": {
+          "type": [
+            "string",
+            null
+          ]
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      },
+      "year": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / timed_out
      Removed value: -{
-  "description": "Whether the search timed out",
-  "type": "boolean"
-}
    • removedOutput schema / properties / took
      Removed value: -{
-  "description": "Time in milliseconds for the search",
-  "type": "number"
-}
    • addedOutput schema / properties / total
      Added value: +{
+  "type": "number"
+}
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "q": "climate change temperature"
-  },
-  {
-    "from": 0,
-    "q": "ocean salinity",
-    "size": 20
-  }
-]New value: +[
+  {},
+  {
+    "from": 0,
+    "size": 20
+  }
+]
  3. Changed4 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"Offset for pagination (default 0)."
    • removedInput schema / properties / q
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Free-text search, e.g. \"ocean temperature\", \"Arctic sea ice\". Omit to browse everything.",
+  "type": "string"
+}
    • addedInput schema / properties / size / description
      Added value: +"Results to return (default 20, max 50)."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond those annotations by specifying the return fields and the broad scientific scope. It does not contradict the annotations and gives the agent a clearer picture of the tool's output.

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 concise and front-loaded, leading with the operation and resource before giving return fields and usage examples. Every sentence earns its place, and the examples are genuinely useful rather than 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?

Given the full schema coverage, strong annotations, and existing output schema, the description provides enough domain context, query examples, and result expectations for an agent to invoke the tool correctly. No critical information appears to be 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?

All three parameters are already documented in the input schema (100% coverage), including defaults and examples. The description reinforces query examples but does not add meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly identifies a specific resource (PANGAEA datasets), a concrete operation (full-text search), and the kinds of fields returned (title, DOI, authors, year, topics). However, it does not explicitly differentiate this tool from closely related siblings such as search_within or facets, so it falls short of full distinction.

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 description provides concrete example query types ('ocean temperature datasets', 'Arctic sea ice cores'), which help an agent understand when this tool is appropriate. It does not explicitly name alternatives or state when to use another tool, so the guidance is clear but not fully contrastive.

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

All Pangaea toolsInspect
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.

Resources