Skip to main content
Glama

Data Reunion

by io.github.pipeworx-io
OverviewAdmin

Query

query
Read-onlyIdempotent

Query records from a Réunion Open Data dataset with ODSQL. Filter (where), aggregate (group_by/select), sort (order_by), paginate (limit/offset).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records (1-100, default 20).
queryNoFree-text keyword across all fields (optional).
whereNoODSQL filter, e.g. `year >= 2020 AND city = "Paris"` (overrides query).
offsetNoPagination offset (default 0).
selectNoODSQL select/aggregation, e.g. `count(*) as n, sum(amount)`.
group_byNoODSQL group_by field(s).
order_byNoSort, e.g. `date desc`.
dataset_idYesDataset id from search_datasets.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dataset_id": "transports-reunion",
+    "limit": 20
+  },
+  {
+    "dataset_id": "transports-reunion",
+    "group_by": "city",
+    "limit": 50,
+    "order_by": "total desc",
+    "select": "count(*) as total",
+    "where": "year >= 2020"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds context about ODSQL usage (filter, aggregate, sort, paginate), which goes beyond annotations and helps the agent understand the tool's query capabilities.

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 sentences, front-loaded with the primary function, and a concise list of capabilities. Every word adds value with no redundancy.

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?

Given the tool has 8 parameters and no output schema, the description covers the main functionality but lacks details on return format, error handling, or dataset availability. It is adequate but not comprehensive.

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 the baseline is 3. The description mentions 'ODSQL' which adds context for parameters like where, select, group_by, but does not significantly enhance understanding of individual parameters 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 clearly states the verb 'Query', the resource 'records from a Réunion Open Data dataset', and the specific capabilities (filter, aggregate, sort, paginate). It distinguishes from sibling tools like search_datasets by specifying ODSQL querying.

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 description implies usage for querying records with ODSQL but does not explicitly state when to use this tool vs alternatives like search_datasets or search_within. No exclusions or when-not-to-use guidance.

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

All Data Reunion toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources