Catalogue Homeoceutics / Homeoceutics Catalog

Catalogue des fiches d'information / Information cards catalog

search_fiches_information

Read-onlyIdempotent

FR : Rechercher ou parcourir les titres des fiches d’information du catalogue public. EN: Search or browse information-card titles in the public catalog.

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": "search_fiches_information"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	FR : Taille de page. EN: Page size.
`query`	No	FR : Texte recherché dans la projection publique sûre ; omettre pour parcourir par titre. EN: Text searched in the safe public projection; omit to browse by title.
`locale`	No	FR : Langue demandée ; les titres indisponibles sont repliés vers le français. EN: Requested language; unavailable titles fall back to French.	fr
`offset`	No	FR : Décalage de page, à reprendre depuis pagination.next_offset. EN: Page offset, continued from pagination.next_offset.
`statut`	No	FR : Statut de visibilité anonyme à filtrer. EN: Anonymous visibility status to filter by.
`categorie`	No	FR : Identifiant exact d’une catégorie, réutilisable depuis categories[].id. EN: Exact category identifier, reusable from categories[].id.

Output Schema

Name	Required	Description
`items`	Yes	FR : Titres et métadonnées uniquement. EN: Titles and metadata only.
`locale`	Yes	FR : Langue demandée pour cette page. EN: Locale requested for this page.
`pagination`	Yes	FR : Pagination déterministe par offset. EN: Deterministic offset pagination.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

changedInput schema / properties / query / description

Previous value: -"FR : Texte recherché dans l’index complet ; omettre pour parcourir par titre. EN: Text searched in the full index; omit to browse by title."New value: +"FR : Texte recherché dans la projection publique sûre ; omettre pour parcourir par titre. EN: Text searched in the safe public projection; omit to browse by title."

addedOutput schema / properties / items / items / properties / acces_praticien_fsm_requis

Added value: +{
+  "description": "FR : true exige un abonnement Pro actif et les déclarations praticien et formation FSM ; aucun achat du pack FSMPro n’est requis. EN: true requires an active Pro subscription plus practitioner and FSM-training declarations; no FSMPro pack purchase is required.",
+  "type": "boolean"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "type",
-  "nom",
-  "categories",
-  "statut",
-  "locale_titre"
-]New value: +[
+  "id",
+  "type",
+  "nom",
+  "categories",
+  "statut",
+  "locale_titre",
+  "acces_praticien_fsm_requis"
+]

First observedSep 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world. The description adds that it operates on a public catalog and only titles, but no additional behavioral traits (auth, rate limits, pagination) are disclosed. With annotations covering the safety profile, a 3 is appropriate.

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 bilingual sentences that are front-loaded and waste no words. The bilingual format is necessary for the locale parameter, and the purpose is stated immediately.

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?

Given six parameters, two enums, and an output schema, the description provides sufficient context about the tool's scope (public catalog, titles only). It does not mention pagination or filtering, but those are covered by the schema and output schema. A minor gap is the lack of sibling differentiation, but overall complete.

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%, so all six parameters are documented in the schema. The description adds no parameter-level details beyond what the schema provides, so baseline 3.

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?

States a specific verb (search or browse) and resource (information-card titles) with scope (public catalog). However, it does not differentiate from the sibling tool search_infoceutiques, which likely covers a different resource, so a 4 rather than 5.

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?

Implies usage by offering search or browse, but does not state when to choose this over alternatives or any exclusions. No explicit when-to-use guidance beyond the verb, so a 3.

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

All Catalogue Homeoceutics / Homeoceutics Catalog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?