Skip to main content
Glama
Sign In

Data Tours

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Datasets

search_datasets
Read-onlyIdempotent

Search Tours Métropole Open Data for datasets by keyword (mobility, urban services & environment). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.

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": {
      "query": "transport"
    },
    "name": "search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax datasets (1-100, default 20).
queryNoKeyword(s) to search dataset titles/descriptions.
offsetNoPagination offset (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "query": "mobility"
-  },
-  {
-    "limit": 50,
-    "offset": 0,
-    "query": "urban services environment"
-  }
-]New value: +[
+  {
+    "query": "transport"
+  },
+  {
+    "limit": 50,
+    "offset": 0,
+    "query": "urbanisme"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "mobility"
+  },
+  {
+    "limit": 50,
+    "offset": 0,
+    "query": "urban services environment"
+  }
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds behavioral output traits (returns specific fields) and domain scope (Tours Métropole Open Data), which is beyond what annotations provide. No contradiction with annotations.

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?

The description is a single, front-loaded sentence that states purpose, scope, and return values without any redundant or filler text. Every element earns its place.

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?

The tool is simple (3 params, no output schema), and annotations cover safety. The description covers purpose, return fields, and a usage hint. It could mention pagination behavior or empty-result handling, but given the simplicity and comprehensive schema/annotations, it is sufficiently complete.

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 100%, so all parameters are documented. The description adds context by providing example keyword categories (mobility, urban services & environment) and mentions the output includes dataset_ids, which indirectly guides parameter use. This goes slightly 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 states a specific verb ('Search'), a resource ('Tours Métropole Open Data'), and a scope ('by keyword (mobility, urban services & environment)'). It also lists the return fields (dataset_ids, titles, themes, record counts) and explicitly mentions passing dataset_ids to query/dataset_info, differentiating it from sibling tools.

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?

The description clearly implies this tool is the entry point for searching datasets by keyword and indicates a downstream workflow ('pass to query/dataset_info'). It does not explicitly state when NOT to use it or name alternatives, but the context is strong enough for an agent to infer appropriate usage.

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

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