Skip to main content
Glama
Sign In

Data Occitanie

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Query records from a Occitanie Region 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": "regional_services_occitanie"
    },
    "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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds no behavioral context beyond the capability list — no default result size, cost/rate considerations, or what an empty/invalid ODSQL result looks like.

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 operation and its domain, with zero filler. The parenthetical capability list is scannable and earns its space.

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?

With 8 parameters, 100% schema coverage and no output schema, the essentials are present. However, nothing describes the shape of returned records, error behavior on malformed ODSQL, or the relationship to search_datasets, which leaves gaps for a query tool that can fail in several ways.

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 every parameter is already documented with examples. The description merely restates the mapping of where/group_by/order_by/limit/offset to filter/aggregate/sort/paginate, adding no syntax or edge-case detail beyond the schema.

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+resource (query records from an Occitanie Region Open Data dataset via ODSQL) and enumerates the operation families (filter, aggregate, sort, paginate). It is clear what the tool does, though it doesn't name a sibling it competes with, so an agent must infer that search_datasets is the discovery counterpart.

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 via the capability list, but no explicit when-to-use or when-not-to-use guidance is given. The dependency on search_datasets for dataset_id appears only in the schema, not in the description, so the workflow prerequisite is not surfaced in the prose.

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

All Data Occitanie 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