Caribbean Data API — Tropical Autonome

by dev.workers.tropicalautonome.tropical-data-api

caribbean_get_marches_publics_dom

Read-only

Marchés publics tous DOM en temps réel — 31 000+ contrats (Guadeloupe 971, Martinique 972, Guyane 973, La Réunion 974, Mayotte 976). DECP officielle. Filtres : département, nature, année. Prix : 0.025 USDC.

Input Schema

TableJSON Schema

Name	Required	Description
`annee`	No	Ex: 2024
`limit`	No	Nombre de résultats (max 100, défaut 20)
`nature`	No	Travaux \| Fournitures \| Services
`offset`	No	Pagination
`departement`	No	971 \| 972 \| 973 \| 974 \| 976
`payment_tx_hash`	No	Hash tx USDC Base (0x+64hex). Absent = instructions paiement.

TDQS

A3.6/5.0

Behavior3/5

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

Annotations include readOnlyHint=true, confirming a safe read operation. The description adds real-time status, official DECP source, and pricing (0.025 USDC), which are beyond annotations. However, it does not disclose pagination behavior, rate limits, or payment flow details beyond the price, leaving some transparency gaps.

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?

The description is a single, tightly packed sentence conveying scope, data volume, specific departments, official status, filters, and price. Every clause adds value, with no redundancy or filler, and key information is front-loaded.

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 retrieval tool with strong annotations (readOnlyHint=true) and full schema coverage, the description adequately covers purpose, scope, filters, and pricing. The absence of an output schema is mitigated by the clear use case, though the payment mechanism (via payment_tx_hash) is only hinted at by the price, leaving minor completeness gaps.

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 the baseline is 3. The description mentions filters (département, nature, année) but only restates schema parameter names without adding deeper semantic meaning or relationships. It does not clarify parameter interactions or value formats beyond what the schema already provides.

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 clearly identifies the resource (public contracts) and scope (all DOM, specific departments enumerated) but lacks an explicit verb like 'list' or 'retrieve'. The tool name includes 'get', so overall purpose is clear and distinguished from the sibling 'caribbean_get_marches_publics' via '_dom' and 'tous DOM'.

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 provides usage context (real-time, all DOM, filters) and notes it covers all DOM, implying use for broader scope. However, it does not explicitly state when to use this over the sibling 'caribbean_get_marches_publics' or any exclusions, so guidance is implied rather than direct.

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

All Caribbean Data API — Tropical Autonome tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Resources

Need Help?