Skip to main content
Glama

NLocale

Lire un article publié du Carnet

lire_article_carnet
Read-onlyIdempotent

Version actuellement publique de l’article dans la langue demandée, avec auteur, sources, statut de visite et éventuel partenariat. La réponse comprend le lien NLocale localisé et la signature publiée, distincte de l’identité des personnes interviewées.

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": {
      "slug": "<slug>"
    },
    "name": "lire_article_carnet"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant d'article du Carnet, en minuscules, chiffres et tirets, tel que renvoyé par rechercher_articles_carnet.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description goes further in disclosing the returned content (author, sources, visit status, possible partnership, localized URL, published signature) and adds a useful caveat that the signature is distinct from interviewees' identity. It still says nothing about failure cases such as an unavailable or unpublished slug/language.

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 sentences, front-loaded with the object and its public/language scope before the return-content details. No filler, though the second sentence is a dense enumeration that could be tightened.

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?

With no output schema, the description takes on the job of describing return values and does so with concrete fields and a notable identity caveat. It falls short only on error/edge behavior (missing language, unpublished article) for an otherwise simple two-parameter read.

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 both parameters are fully documented, including the slug pattern and the language enum, so the schema carries the load. The description adds only a paraphrase of the language dimension ('dans la langue demandée') and no extra semantics beyond the schema.

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 identifies the resource precisely: 'Version actuellement publique de l'article' plus the requested-language dimension, which distinguishes it from any internal/draft representation. It is a noun phrase rather than a verb+resource statement and never names a sibling such as rechercher_articles_carnet, so differentiation is only partial.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named; the only implicit signal is 'version actuellement publique', which suggests reading a published article rather than a draft. An agent must infer that this is the follow-up call to a search by slug.

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