Skip to main content
Glama

SizeMyFile

Group and aggregate data

data_aggregate
Idempotent

Group rows by one column and calculate count, sum, average, minimum or maximum for a numeric field. Up to 32 MiB input, 50,000 rows and 200 columns. CSV cells remain strings unless an operation explicitly parses numeric values. No uploaded code is executed. Null and empty numeric cells are excluded from numeric aggregates. Non-numeric values cause an error. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "data_aggregate"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: 32 MiB/50,000 row/200 column limits, CSV cells treated as strings unless parsed, no uploaded code execution, null/empty numeric cells excluded, non-numeric values raise an error, queued run returning an ID, and cloud allowance consumption. Nothing here contradicts the declared readOnlyHint=false / idempotentHint=true / destructiveHint=false profile.

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?

Front-loaded with the core operation, then constraints and behavioral caveats in short declarative sentences. Every line carries information, though 'No uploaded code is executed' and 'Uses cloud allowance' are only loosely tied to the stated operation and could be tightened.

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?

An output schema exists, so return values need not be explained, and the description still notes that a run ID comes back for tracking. Gaps remain around the artifacts input (the actual data source) and the idempotency-key contract, but overall it is sufficient for a queued aggregation job.

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 coverage is 0%, so the description carries the burden. It does explain the semantics of group, column, and operation (including the count/sum/mean/min/max set) and the string-vs-numeric caveat, but never mentions artifacts (which files to aggregate), idempotency_key, format (csv/json/parquet), or allow_server_fallback.

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 gives a concrete verb and resource: group rows by one column and compute an aggregate over a numeric field, listing the five supported operations. That is enough to tell it apart from data_join or data_profile, although no sibling is named 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?

Usage is only implied by the operation described; there is no statement of when to prefer this over data_query, data_profile, or data_join, and no prerequisites beyond the size limits. The limits and error behavior help an agent decide if a call is viable but not which tool to pick.

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.