Skip to main content
Glama
Sign In
mcp-data-gouv-fr

mcp-data-gouv-fr

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

data_gouv_fr_fetch_source_excerpt

Retrieve a concise text excerpt from a selected French open data source by matching its index, title, or URL, enabling quick content verification without full downloads.

Instructions

Fetch a short text excerpt from one curated source URL. Use source_key as a number, title keyword, or URL fragment from get_sources.

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": {
      "source_key": "<source_key>"
    },
    "name": "data_gouv_fr_fetch_source_excerpt"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNoMaximum excerpt length.
source_keyYesSource index, title keyword, or URL fragment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does so reasonably well by stating it 'Fetch[es]' a 'short text excerpt', which implies a read-only, benign operation with a bounded return size. However, it could elaborate on error handling, rate limits, or what happens with invalid keys.

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?

Two sentences, completely void of fluff. The first sentence states the core purpose, the second provides essential usage direction. Every word serves a purpose. An exemplary model of concise, front-loaded writing.

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 simple 2-parameter tool with no output schema and no annotations, the description covers the essentials: what is fetched, from where, and how to construct the key. The only minor gap is not explaining the max_chars parameter's purpose or default, but that's adequately handled by the schema. The guidance is complete enough for effective tool selection and invocation.

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 coverage is 100% with clear parameter descriptions ('Source index, title keyword, or URL fragment' and 'Maximum excerpt length.'). The description adds marginal value by reinforcing the source_key format and connecting it to get_sources, but this doesn't go far beyond what the schema already provides. 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?

Uses a specific verb-resource pairing: 'Fetch a short text excerpt from one curated source URL.' This distinguishes it from siblings that search or list datasets/organizations, and the mention of 'curated source URL' plus the reference to get_sources clearly positions it as a focused retrieval tool.

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 gives clear context that source keys originate from get_sources ('...or URL fragment from get_sources'), providing a dependency pointer to a sibling tool. It doesn't explicitly state when NOT to use it or name alternatives for exclusions, but the guidance on key construction is actionable for an agent.

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