Skip to main content
Glama

NLocale

Lire une fiche publique et ses sources

lire_fiche_publique
Read-onlyIdempotent

Détails factuels de la clé retournée par une recherche, après vérification de la publication actuelle. La réponse comprend le lien NLocale et les sources originales, avec des champs distincts pour la récupération, la validation documentaire, l’identité et la visite.

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": {
      "key": "<key>"
    },
    "name": "lire_fiche_publique"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesClé exacte renvoyée par une recherche, de la forme type:identifiant, avec type égal à event, business, municipality, place ou content.
langueNoLangue de la réponse : fr, en, de, nl, it ou es. Défaut : fr. Une langue absente n'est pas remplacée par le français.fr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real context by disclosing the live publication re-check and the structure of the returned payload (NLocale link, original sources, separate retrieval/validation/identity/visit fields), which annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loading the purpose and then the response contents. The closing enumeration of field categories ('récupération, validation documentaire, identité, visite') is slightly abstract jargon, but it is not padded.

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 two-parameter read tool with full annotation coverage, the definition is nearly complete, and since no output schema exists, its description of the returned sections is genuinely useful. The language fallback behavior is left to the schema rather than the description, which is acceptable.

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%, so the format of 'key' and the language enum are already fully documented. The description adds only a light constraint — that the key must stem from a search and still be published — and says nothing extra about the language parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: retrieving factual details for a key produced by a search, with a re-check of current publication status. It implicitly separates this detail-fetch from the search siblings via 'clé retournée par une recherche', but never names a specific alternative 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?

It establishes the workflow prerequisite clearly: the parameter must be a key returned by a prior search, and the publication status is re-verified at read time, implying stale keys may behave differently. No explicit when-not-to-use or named alternative is given, keeping it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources