Skip to main content
Glama
Sign In

Catalogue Homeoceutics / Homeoceutics Catalog

by com.homeoceutics
OverviewDiscussionsAdmin

Catalogue des infoceutiques / Infoceutics catalog

search_infoceutiques
Read-onlyIdempotent

FR : Rechercher ou parcourir les titres des infoceutiques du catalogue public. EN: Search or browse infoceutic 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_infoceutiques"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFR : Taille de page. EN: Page size.
queryNoFR : 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.
localeNoFR : Langue demandée ; les titres indisponibles sont repliés vers le français. EN: Requested language; unavailable titles fall back to French.fr
offsetNoFR : Décalage de page, à reprendre depuis pagination.next_offset. EN: Page offset, continued from pagination.next_offset.
statutNoFR : Statut de visibilité anonyme à filtrer. EN: Anonymous visibility status to filter by.
categorieNoFR : Identifiant exact d’une catégorie, réutilisable depuis categories[].id. EN: Exact category identifier, reusable from categories[].id.

Output Schema

NameRequiredDescriptionDefault
itemsYesFR : Titres et métadonnées uniquement. EN: Titles and metadata only.
localeYesFR : Langue demandée pour cette page. EN: Locale requested for this page.
paginationYesFR : Pagination déterministe par offset. EN: Deterministic offset pagination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this is a public catalog, but says nothing about pagination behavior or result limits beyond the schema.

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?

Very short and front-loaded, with the FR and EN statements carrying identical content. The bilingual duplication is redundant but consistent with the bilingual schema field descriptions, and nothing is wasted or buried.

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 read-only, zero-required-parameter catalog search with a full output schema, an agent has everything needed: resource scope, search-vs-browse behavior from the schema, and pagination fields. Only cross-tool routing to search_fiches_information is missing.

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 already documented with their limits, enums, defaults and pagination semantics. The description adds no meaning beyond the schema, so the 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 verb (search/browse) and resource (infoceutic titles in the public catalog), so the agent knows exactly what is retrieved. It does not distinguish itself from the sibling search_fiches_information, which searches a different resource, leaving the differentiation to be inferred.

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?

'Search or browse' implies the two modes, and the schema's query description clarifies that omitting query browses by title, but the description itself gives no explicit when-to-use, prerequisites, or which sibling to prefer. Usage is implied rather than stated.

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 toolsInspect
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