Catalogue public anonyme en lecture seule. Anonymous, read-only public catalog.
FR : Rechercher ou parcourir les titres des fiches d’information du catalogue public. EN: Search or browse information-card titles in the public catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | FR : Taille de page. EN: Page size. | |
| query | No | FR : Texte recherché dans l’index complet ; omettre pour parcourir par titre. EN: Text searched in the full index; 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. |
| 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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the public-catalog and title-level scope, and does not disclose additional behaviors such as result ordering, pagination behavior, or locale fallback beyond what the schema already documents.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded, using two short bilingual sentences with no filler. The FR/EN duplication is justified by the bilingual context, though it leaves behavioral and selection detail to the schema and annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only catalog search tool, the schema and annotations carry most of the burden and are quite complete. However, the description does not differentiate this tool from its only sibling, search_infoceutiques, and does not clarify whether results contain only titles or fuller card content, leaving a meaningful selection gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents every parameter, including enums, defaults, and cross-references like pagination.next_offset and categories[].id. The tool description itself contributes no parameter-level meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Rechercher ou parcourir' the 'titres des fiches d’information du catalogue public'. It clearly identifies what the tool acts on and that it covers public information-card titles, though it does not explicitly contrast with the sibling tool search_infoceutiques.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies a search-versus-browse distinction, reinforced by the query parameter's note to 'omit to browse by title'. However, it does not state when to prefer this tool over search_infoceutiques or provide exclusion criteria, so usage guidance is mostly implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
FR : Rechercher ou parcourir les titres des infoceutiques du catalogue public. EN: Search or browse infoceutic titles in the public catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | FR : Taille de page. EN: Page size. | |
| query | No | FR : Texte recherché dans l’index complet ; omettre pour parcourir par titre. EN: Text searched in the full index; 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. |
| 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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context beyond that, mainly the 'public catalog' scope, but does not describe any extra behavior such as result handling or fallbacks.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, bilingual, and front-loaded with the action and resource. Every sentence earns its place, and the FR/EN duplication is intentional for the target audience.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich schema, the output schema, and the annotations, the description is nearly complete for safe invocation. It could more explicitly steer between this tool and search_fiches_information, but the public-catalog and titles context is enough for an agent to proceed correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all six parameters, including pagination offsets, locale fallback, and category filtering. The description itself adds no parameter-level detail, which is acceptable per the baseline for full schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb pair ('search or browse') and a specific resource ('infoceutic titles in the public catalog'), making the tool's purpose clear. It does not explicitly differentiate from the sibling search_fiches_information, but the public-catalog/titles scope is distinct enough to avoid major ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly states the tool is for searching or browsing infoceutic titles in the public catalog, giving the agent a concrete usage context. It does not mention when not to use it or point to alternatives, but the public-catalog and title scope is sufficient guidance for basic selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Search and browse the BAM Kaarsen candle catalog and white-label offering. Read-only, no auth.
Read-only Tudetic product search and vehicle compatibility with safe public pricing.
Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication.
Read-only IDFMETALE precious-metals catalog: live spot prices, availability, VAT status.
Add one secure layer between your agents and this server.
The two tools are clearly distinct by content type: one searches information-card titles, the other searches infoceutic titles. No overlap or ambiguity between them.
Both tool names follow the same 'search_' + plural noun pattern, making the naming scheme predictable and consistent.
With only 2 tools, the set feels thin, even though each tool covers one of the two catalog categories. It is borderline but not excessively under-scoped.
The catalog domain would naturally benefit from retrieval of full details for individual items, not just title search. The tools cover only title-level browsing, leaving notable gaps for agents needing complete catalog information.
