Skip to main content
Glama

Pangaea Recent

pangaea_recent
Read-onlyIdempotent

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

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": {
      "days": 30,
      "size": 10
    },
    "name": "pangaea_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOnly datasets registered within the last N days (optional).
sizeNoHow many (default 20, max 50).

Output Schema

NameRequiredDescriptionDefault
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the ordering behavior (newest DOI registrations first), which is genuinely useful, but says nothing about pagination, rate limits, or result volume beyond what the schema states.

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 sentence with zero filler, and the scoping information (recency, ordering) is front-loaded. Nothing is repeated or wasted.

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?

With an output schema, full parameter documentation, and rich annotations, this simple read-only feed needs little prose; the definition is adequate to call the tool correctly. The one meaningful gap is sibling differentiation, which leaves the agent to guess when to prefer pangaea_search or pangaea_dataset instead.

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 both optional parameters documented including the size default of 20 and max of 50. The description adds no parameter-level meaning beyond that baseline; its ordering note lightly reinforces what the days filter implies but does not explain edge cases.

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 names the resource (PANGAEA datasets) and its precise scope (most recently published, newest DOI registrations first). It is clearer than a bare name, but it never distinguishes itself from siblings like pangaea_search or pangaea_dataset, so an agent must infer that this is the recency feed.

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?

"Most recently published" implicitly signals when to use it — when the agent wants the newest datasets rather than a query-driven search. There is no explicit when-not guidance and no named alternative such as pangaea_search for filtered lookups, so routing between siblings is left to inference.

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.