Skip to main content
Glama
Sign In

Data Grandparissud

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "dataset_id": "public_transport_stops"
    },
    "name": "query"
  }
}

Input 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.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered by structured data. The description's only added behavioral signal is that aggregation is supported, which is genuinely useful, but it says nothing about rate limits, result size behavior, or error handling.

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?

Two compact sentences, front-loaded with the core verb and resource, and the capability list is telegraphic rather than verbose. It does not waste words, though the second sentence reads as a parameter enumeration.

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 an 8-parameter tool with no output schema, the description covers what querying supports but omits return shape, pagination behavior, and how this tool relates to sibling search/discovery tools. Combined with fully documented params and rich annotations, this is adequate but not complete.

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% and each parameter is documented with examples, so the schema already does the heavy lifting. The description's parenthetical mapping of where/group_by/order_by/limit to their roles largely restates that schema content.

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?

States a specific verb (query) and resource (records from a Grand Paris Sud Open Data dataset) plus the query dialect (ODSQL). It does not explicitly differentiate itself from nearby siblings like search_within or dataset_info, which is the only thing keeping it from a 5.

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 capability list (filter, aggregate, sort, paginate) implies when to use it, but there is no explicit when/when-not guidance and no named alternative such as search_within or search_datasets. Usage is inferable but not stated.

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

All Data Grandparissud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources