List supported Jumia country storefronts with their domains and currencies so you can choose valid country values for Jumia search and category queries.
List supported Jumia country storefronts. Returns the Jumia country storefronts accepted by the country parameter on jumia-search, jumia-category and jumia-categories, with each storefront's domain and currency. Static metadata.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.16Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It does so by labeling the data as 'Static metadata,' which implies a safe read-only operation with stable results, and by stating the return fields (domain and currency). It does not discuss auth or rate limits, but for a static zero-parameter metadata tool this is adequate.
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?
Three short sentences, front-loaded with the core purpose. Each sentence adds useful detail without repetition: what it lists, where those values are used, and what fields are returned.
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 a zero-parameter tool with no output schema, the description fully explains what is returned (supported storefronts with domain and currency), that the data is static, and how it connects to sibling tools. Nothing needed to call it correctly is missing.
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 tool takes zero parameters, so the baseline is 4. The description appropriately focuses on the output shape (domain and currency per storefront) and how the returned values relate to parameters on other tools.
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?
States a specific verb and resource: 'List supported Jumia country storefronts.' It also distinguishes itself from siblings by naming the country parameter on jumia-search, jumia-category, and jumia-categories, making its role immediately clear.
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?
Explains the practical use case: obtaining the storefronts accepted by the country parameter on related Jumia tools. It provides clear context for when to call it but does not explicitly state exclusions or alternatives beyond the implied relationship.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.