Paperasse MCP

get_fiche

Retrieve the complete official service-public.fr fiche text by ID to answer French administrative procedure questions with verbatim wording and citable links.

Instructions

Read the full official text of a service-public.fr fiche, by id (e.g. "F12006").

Use after search_fiche, before answering. The text is the official wording, in French,
with Markdown headings and [links](url). It often covers several cases ("### En France",
"### À l'étranger"): pick the one that matches the user's situation. When the official text
repeats a block word for word in several cases, it is given once; later copies are replaced by
a line "[Paperasse : identique à « … » plus haut (sous « … »)]" pointing to the first copy.

Returns title, url, urls (the official page on each site, for fiches written for both
individuals and professionals), updated_at, text, online_services (official online procedures with
links) and sources (legal texts). Long fiches come in pages: if `next_offset` is not null,
call again with offset=next_offset to read more. For paged fiches, `outline` lists the
main headings with their offset: call get_fiche(id, offset=...) to jump to a section.

Input Schema

Name	Required	Description	Default
`id`	Yes
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that the text is official French wording with Markdown headings and links, that multiple cases may appear, how repeated blocks are deduplicated with a specific placeholder line, and what fields are returned including pagination and outline behavior.

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 front-loaded with purpose, then usage, then return and pagination details. Despite its length, every sentence provides useful operational context for a tool with multi-case text, deduplication, and paged output.

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?

Even though an output schema exists, the description adds important context about return fields and paging behavior that helps an agent use the tool correctly. Given the absence of annotations and the complexity of paged, multi-case official text, the description is complete enough to call the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does. It explains the id parameter with a concrete example format and explains offset through the pagination and outline mechanisms, including how to jump to a section with get_fiche(id, offset=...).

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 precise verb and resource: 'Read the full official text of a service-public.fr fiche, by id.' It includes an example id and distinguishes the tool from its sibling by saying to use it after search_fiche. An agent can identify exactly what this tool does and when it follows search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool after search_fiche and before answering, and explains how to handle multi-case fiches by picking the case matching the user's situation. It also gives clear pagination instructions: if next_offset is not null, call again with offset=next_offset, and explains outline-based section jumping.

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

Deploy Server