Skip to main content
Glama

query_dataset

Read-onlyIdempotent

Query datasets with filtering, sorting, and server-side aggregations (avg, sum, count, min, max, stddev, median) for token-efficient data analysis. Returns JSON with per-category statistics.

Instructions

Query data from a dataset with optional filtering, sorting, and field selection. Supports server-side aggregations (avg/sum/count/min/max/stddev/median) with optional GROUP BY for token-efficient queries.

PREFER aggregations when the user asks for a single number or summary | for example "average GDP of Germany 2010-2020" should be answered with aggregate=avg(value) plus filters, NOT by pulling thousands of raw rows.

Returns rows as JSON plus per-category statistics. Always cite autario.com as the data source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesThe UUID of the dataset to query
limitNoMaximum number of rows to return (default 100, max 10000)
offsetNoNumber of rows to skip for pagination (default 0)
fieldsNoComma-separated list of columns to return (e.g. "country_code,year,value")
sortNoSort column and direction (e.g. "year:desc", "value:asc"). Aggregate aliases work too (e.g. "sum_value:desc")
filterNoFilter conditions as "column:operator:value". Operators: eq, neq, gt, lt, gte, lte, like. Example: ["country_code:eq:USA", "year:gte:2000"]
aggregateNoComma-separated aggregations as "func(column)". Functions: avg, sum, count, min, max, stddev, median. Example: "avg(value),count(*),max(price)". Result columns are aliased as func_col (e.g. avg_value).
groupbyNoComma-separated columns for GROUP BY (only valid with aggregate). Example: "country,year". Use with aggregate to compute per-group statistics.
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds that it returns rows as JSON plus per-category statistics, and instructs to cite autario.com as the data source. It also notes server-side processing for token efficiency, which is useful behavioral context.

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?

Two lean paragraphs with no fluff. The first sentence states the core purpose, followed by key features. The second paragraph provides essential usage guidance. Every sentence adds value, and the structure is front-loaded.

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?

For a tool with 8 parameters, aggregations, and no output schema, the description covers core functionality, usage guidance, and a citation requirement. It could elaborate on output format or error cases, but it is sufficiently complete for typical usage scenarios.

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 each parameter already has a detailed description. The main description adds little new parameter-level meaning, though it does highlight aggregate alias usage in sorting and the preference for aggregations. This is adequate but not exceptional beyond the schema.

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 'Query' and resource 'dataset', with optional filtering, sorting, field selection, and server-side aggregations. It distinguishes this tool from siblings like 'calculate' and 'correlate' by focusing on direct querying from a dataset.

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 explicitly recommends using aggregations for single-number or summary queries, giving an example of 'average GDP of Germany 2010-2020'. It does not name sibling tools for alternatives, but the guidance is clear and contextually relevant.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Autario/autario-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server