Skip to main content
Glama

NLocale

Rechercher les articles publiés du Carnet

rechercher_articles_carnet
Read-onlyIdempotent

Rencontres, coulisses et récits publiés par NLocale dans la langue demandée, avec auteur réel, sources et dates. Français, anglais, allemand, néerlandais, italien et espagnol. Aucun brouillon ni remplacement par une autre langue. Les slugs retournés donnent accès aux articles détaillés.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximal de résultats, de 1 à 20. Défaut : 10 (20 pour agenda_weekend).
queryNoMots recherchés, 160 caractères au plus. La recherche porte aussi sur les termes français de la même publication ; la réponse reste dans la langue demandée.
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
offsetNoDécalage de pagination. Défaut : 0. Le maximum est 500, sauf pour rechercher_articles_carnet (10000). La réponse donne pagination.total et pagination.next_offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: only published articles are returned (no drafts), the requested language is never silently substituted, and the response carries real author, sources and dates — details not derivable from annotations.

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?

Four short, front-loaded sentences that lead with what is returned, then language coverage, then the anti-fallback constraint, then the slug follow-up. Minor redundancy in listing all six languages, which the enum already provides.

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?

All parameters are optional and documented, and with no output schema the description appropriately sketches the return shape (author, sources, dates, slugs) plus pagination handled by the schema. Adequate for a read-only search endpoint; only the lack of sibling routing guidance keeps it from full marks.

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 all four parameters are already documented, including the language enum and its no-fallback rule. The description's language paragraph largely restates the schema rather than adding new semantics beyond confirming the no-substitution guarantee.

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 names the content type ("Rencontres, coulisses et récits publiés par NLocale"), the language scope, and the returned payload (auteur réel, sources, dates, slugs). It implicitly distinguishes itself from lire_article_carnet by noting the slugs lead to the detailed articles, though the search verb itself is never stated explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: you call it to obtain article slugs that then give access to full articles via the reader tool. There is no explicit when-to-use versus the sibling search tools (rechercher_contenus_publics, rechercher_etablissements, etc.), so the agent must infer the routing.

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