Skip to main content
Glama
Sign In

Data Tours

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dataset Info

dataset_info
Read-onlyIdempotent

Get metadata for one Tours Métropole Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.

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": {
      "dataset_id": "tours-metro-bike-stations"
    },
    "name": "dataset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_idYesDataset id from search_datasets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dataset_id": "tours-metro-bike-stations"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, confirming safe read behavior. The description adds context about the metadata returned (fields/schema, themes, record count), enhancing transparency without contradicting 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 conveys all necessary information without waste. Every part serves a purpose, earning a top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one required parameter, no output schema, and rich annotations), the description provides sufficient context about what the tool does and when to use it. No additional information is needed.

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 the tool description reinforces the parameter's role by mentioning 'dataset_id' contextually. However, it does not add significant new meaning beyond the schema's description 'Dataset id from search_datasets'. Baseline 3 is appropriate.

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 'Get' and the resource 'metadata for one Tours Métropole Open Data dataset', listing specific metadata elements like fields/schema, themes, and record count. It also distinguishes from siblings by advising 'call before query to learn the column names', which differentiates it from query and search 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 explicitly indicates when to use the tool ('call before query to learn the column names'), providing clear context. However, it does not explicitly state when not to use it or provide alternatives, though the purpose is well-defined.

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