Retourne la carte complète d'un fournisseur : description, endpoints, prix, statut vérification. Gratuit.
| Name | Required | Description | Default |
|---|---|---|---|
| provider_slug | Yes | Identifiant fournisseur (ex: agri-guadeloupe) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not required to restate safety. It adds the fact that the tool is 'Gratuit' (free) and lists the types of information returned, which provides some additional context. However, it does not disclose potential limitations, rate limits, or data freshness.
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 a single, front-loaded sentence that directly states the tool's purpose and key outputs. Every word contributes meaning, with no redundancy or filler.
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 simplicity of the tool (one parameter, no output schema), the description adequately covers what the tool returns. It lists the main fields but could be slightly clearer about what a 'provider' refers to in this context. Overall, it is sufficient for a basic read-only lookup tool.
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?
The schema provides 100% coverage for the single parameter provider_slug, including an example. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.
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 clearly states the tool's purpose: returning a provider's full card including description, endpoints, prices, and verification status. The verb 'Retourne' is specific, and the resource is identified as a provider. It distinguishes itself from sibling tools by focusing on provider metadata rather than specific data topics.
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 when to use the tool (to get provider details) but does not explicitly state when not to use it or mention alternatives. There is no direct comparison to sibling tools, though the context suggests this is for provider information. Clear but not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct domains (solar, biodiversity, water, etc.), but the pair caribbean_get_marches_publics and caribbean_get_marches_publics_dom overlap significantly, differing only in geographic scope. The sub-group of 'caye' tools (marche, vanille, vetiver) are also thematically similar, though descriptions clarify their specific commodities. Overall, an agent could generally select correctly, but a few boundary cases exist.
The tools overwhelmingly follow a caribbean_get_<subject> convention, with only two exceptions: caribbean_analyse_solaire (uses 'analyse' instead of 'get') and caribbean_list_marketplace (uses 'list' instead of 'get'). This makes the pattern predictable and readable, with minor deviations that are still intuitive. The subject names are consistently descriptive, though some use abbreviations like 'dom' and 'oa' that might require context.
24 tools is on the heavy side for a single server, particularly given that many tools are single-purpose data lookups (e.g., biodiversity, eDNA, tourism). The count is justifiable for a wide-ranging Caribbean data API, but it risks overwhelming an agent with a large surface. It is not excessive enough to be absurd, but it's in the 'heavy' zone.
The server covers multiple domains comprehensively, such as solar energy (tariffs, irradiation, connection, tax credit, financing) and public contracts (Guadeloupe and all DOM). The marketplace meta-tools (llms_txt, list_marketplace, get_provider) ensure discoverability, but there is no general search or aggregation tool. Some areas like agriculture or real estate beyond what's present could be considered gaps, but the core coverage is solid.