Skip to main content
Glama

Pangaea Facets

pangaea_facets
Read-onlyIdempotent

Aggregate matching datasets by a facet, top values of a category field (e.g. "agg-mainTopic", "agg-author", "agg-method", "agg-location", "agg-campaign") with counts. Optionally scoped to a full-text query.

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": {
      "field": "source"
    },
    "name": "pangaea_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoTop-N buckets (default 25).
fieldYesA keyword facet field, e.g. "agg-mainTopic", "agg-author".
queryNoOptional full-text scope for the aggregation.

Output Schema

NameRequiredDescriptionDefault
hitsNo
tookNo
_shardsNo
timed_outNo
aggregationsNoAggregation results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld behavior, so the safety profile is covered. The description adds that results are top-N values 'with counts' and that the scope is optional, but says nothing about missing/unknown facet fields, bucket truncation beyond the size parameter, or ordering of results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the operation front-loaded and the optional scoping condition placed after it. Slightly awkward phrasing ('Aggregate matching datasets by a facet, top values of a category field') but no redundant filler.

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?

A three-parameter read-only aggregation tool with full schema coverage and an output schema; the description covers purpose, scoping and result shape sufficiently. Only minor gaps remain, such as ordering or handling of empty/unknown facet fields.

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%, so field, size and query are already documented. The description's example facet names repeat what the schema already shows, adding no new semantics such as field naming rules or whether unaggregatable fields fall back to something else.

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?

Names a specific operation (aggregate matching datasets by a facet, returning top values with counts) and the resource (Pangaea facet fields). It implicitly separates itself from sibling search/dataset tools by being the counting/aggregation endpoint, but never names those siblings explicitly.

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 phrase 'optionally scoped to a full-text query' hints at when the query parameter matters, but there is no explicit guidance on when to use this versus pangaea_search or pangaea_dataset, and no stated prerequisites or exclusions.

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.