Skip to main content
Glama
musharna

data-aggregator-mcp

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

operate

Read-only

Inspect or query remote Parquet/CSV/TSV files without downloading: get schema, preview/head rows, run read-only SQL, or profile columns by catalog ID and file name.

Instructions

Inspect or query a remote tabular file (Parquet/CSV/TSV) WITHOUT downloading it. op='schema' returns columns+types; 'preview' a small sample; 'head' the first n rows; 'sql' a read-only SELECT against the file (exposed as the view 'data', e.g. "SELECT * FROM data WHERE x > 1"). op='peek' profiles every column WITHOUT downloading — type, null-rate, approximate distinct count, min/max, and numeric quartiles (a DuckDB SUMMARIZE; like head/sql it reads the whole file, so it honors the source-size ceiling). Addresses a file by catalog id + file name (resolve the id first to see files[] and access_modes). Requires the [operate] extra; fails loud if the file is not an operable tabular file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoRow count for head/preview
idYesDataResource id (e.g. 'zenodo:7654321')
opYes
fileNoFile name within the record; optional when exactly one operable file is present.
queryNoRead-only SELECT for op='sql'.
columnsNoOptional column projection for head.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.54.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.46.0
    • addedInput schema / properties / n / minimum
      Added value: +1
  3. Changed1 schema field changedv0.40.0
    • changedInput schema / properties / op / enum
      Previous value: -[
-  "schema",
-  "preview",
-  "head",
-  "sql"
-]New value: +[
+  "schema",
+  "preview",
+  "head",
+  "sql",
+  "peek"
+]
  4. Addedv0.20.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior beyond that: SQL is restricted to read-only SELECT against the view 'data', peek/head/sql read the whole file and therefore honor a source-size ceiling, the tool requires the [operate] extra, and it fails loud on non-operable files. This is exactly the extra context annotations cannot carry.

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?

Dense but every clause carries information; the no-download constraint and op list are front-loaded before the addressing/permission details. Slightly long as a single paragraph, but nothing is padding.

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 no output schema, the description does the work of describing what each op returns, and covers the addressing model, extra requirement, and failure mode. A couple of minor gaps remain (e.g. default n behavior and pagination/limits on sql results) but the tool is callable correctly as written.

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

Parameters4/5

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

Schema coverage is already 83%, but the description adds real meaning the schema lacks: it defines each op value's semantics and output (columns+types, small sample, first n rows, read-only SELECT, full profiling with null-rate/distinct/min-max/quartiles). It also explains the SQL view alias 'data' and its example, which the schema does not.

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?

States a precise verb+resource ('Inspect or query a remote tabular file') plus the key differentiator ('WITHOUT downloading it') and enumerates the five operations with their distinct return shapes. An agent can distinguish it from fetch (which downloads) and from search/resolve without opening the schema.

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?

Gives clear operational routing: resolve the id first to see files[] and access_modes, notes the [operate] extra requirement, and notes file is optional when exactly one operable file exists. It stops short of explicitly naming the sibling alternative (e.g. fetch) that would be used when download is desired, so it is clear context but not full when/when-not coverage.

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

Deploy Server

Other Tools