Skip to main content
Glama
Wobani034

Le Parrain MCP

by Wobani034

Rechercher des programmes de parrainage

search_programs

Search referral programs by keyword and obtain the correct referral link, personalized if you are connected.

Instructions

Cherche des programmes de parrainage dans l'annuaire Le Parrain. Renvoie pour chaque résultat le bon lien de parrainage (le vôtre si vous êtes connecté et l'avez publié, sinon le lien par défaut).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesMot-clé : nom de marque, catégorie, secteur…
Behavior3/5

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

With no annotations, the description bears full burden. It discloses the key behavior of returning a personalized link based on user login and publication status. However, it omits other traits like pagination, error handling, or authentication requirements.

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 concise sentences, front-loaded with the action verb 'Cherche' and clearly structured. Every sentence adds essential information without redundancy.

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 simple search tool with one parameter and no output schema, the description is fairly complete. It covers the core functionality and the unique link behavior. Could mention result format or edge cases, but not critical.

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% for the single parameter 'query', which already has a description. The tool description adds no additional semantic detail beyond restating the keyword concept, so it adds minimal value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for sponsorship programs in a specific directory and returns results with personalized links. This distinguishes it from siblings like get_program (single program) and search_blog (blog search).

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?

The description implies usage for finding sponsorship programs but does not explicitly state when to use this tool over alternatives like suggest_program or when not to use it. No exclusions or context for alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Wobani034/leparrain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server