Skip to main content
Glama
Sign In
mcp-french-transport-data

mcp-french-transport-data

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

french_transport_data_get_dataset

Retrieve a specific French transport dataset by its ID to get detailed information for analysis or integration.

Instructions

Fetch one transport.data.gouv.fr dataset by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "french_transport_data_get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDataset id from french_transport_data_search_datasets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Fetch' correctly signals a read-only, single-resource retrieval, but it does not disclose failure behavior, response shape, or any service-specific caveats. It is minimally sufficient for a simple GET-style tool.

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?

One active sentence with no filler. The verb, resource, and selection key are all front-loaded, making the tool's purpose immediately understandable.

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?

For a tool with one required parameter and a straightforward retrieval purpose, the description plus schema is sufficient for a basic call. It could mention expected output or not-found behavior, but complexity is low and no output schema was provided.

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?

The schema already documents the single parameter with 100% coverage, so the baseline applies. The tool description adds no parameter details beyond what the schema provides; the meaningful source-of-id instruction lives in the schema, not the description.

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?

Description names the exact resource (dataset) and retrieval action, and specifies selection by id. It clearly distinguishes from siblings: search_datasets returns lists, while this retrieves a single dataset; get_sources and fetch_source_excerpt serve different resources.

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 does not explicitly name alternatives, but the parameter schema states the id must come from french_transport_data_search_datasets, establishing the intended workflow. This gives clear context even though it lacks explicit 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.

Deploy Server

Other Tools