Skip to main content
Glama

Free Official Data Samples, Provenance, Aggregations & Insights

Aggregate an official dataset

aggregate_imported_dataset
Read-onlyIdempotent

Free preview returns the top 10 groups over the published snapshot; paid auth raises the bound to top 50. Use for deterministic count, sum, average, minimum, or maximum groups with dataset provenance instead of downloading rows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset_id": "<dataset_id>",
      "group_by": "<group_by>"
    },
    "name": "aggregate_imported_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
fieldNo
metricNo
group_byYes
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior beyond the annotations: free preview returns top 10 groups, paid auth raises the bound to top 50, and results are computed over the published snapshot with dataset provenance.

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 two compact sentences with no filler. The auth/output-bound constraint is front-loaded, followed by the intended use case, so the important information is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter aggregation tool with no schema descriptions and no output schema, the definition covers purpose, metric options, and preview limits. However, it leaves important parameter semantics for field, group_by, and dataset_id underspecified and does not describe the result structure beyond 'top groups.'

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only partially does. It clarifies the 'top' bound and lists the 'metric' enum values, and it implies grouping via 'groups,' but it does not explain dataset_id, group_by, or field, including whether 'field' is the column used by sum/avg/min/max.

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 uses a specific verb, 'aggregate,' with a clear resource, 'official dataset,' and explains the operation as deterministic grouped metrics with dataset provenance. It distinguishes this from row-level retrieval by explicitly recommending it 'instead of downloading rows.'

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?

It gives clear usage context: use this for deterministic count/sum/average/min/max grouped results instead of downloading rows. It also explains the free-preview and paid-auth output bounds. It does not explicitly name when to use sibling tools such as query_imported_dataset, but the row-download alternative is sufficient guidance.

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.

Resources