Is an African exchange open right now? Returns reason (hours/weekend/public holiday with name), local time, session, and next open/close. Handles Sun–Thu markets and holidays.
| Name | Required | Description | Default |
|---|---|---|---|
| exchange | Yes | Exchange code, e.g. NGX, JSE, EGX. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a safe, read-only, idempotent operation. The description adds valuable behavioral context by listing the exact output fields (reason, local time, session, next open/close) and disclosing that Sun–Thu markets and holidays are handled. No contradictions with annotations.
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, front-loaded with the purpose question, and each sentence adds relevant information—purpose, return fields, and market handling—without any wasted words.
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 tool's simplicity (one parameter, read-only, with annotations), the description is complete for an agent to understand what it does and what it returns. It explicitly lists the return fields and notes holiday handling, which is sufficient in the absence of an output schema.
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 input schema fully covers the single parameter 'exchange' with examples (NGX, JSE, EGX), so schema coverage is 100%. The description does not add any additional meaning about the parameter itself, meriting the baseline score of 3.
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 function: checking if an African exchange is open right now. It specifies the resource (African exchange) and the return content (reason, local time, session, next open/close), distinguishing it from sibling tools like get_ngx_market_status by its African-wide scope.
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 the use case (checking market open status for African exchanges) and notes a limitation (handles Sun–Thu markets and holidays), but it does not explicitly state when to use this tool versus alternatives or when not to use it. No alternatives are named.
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.
Tools are largely distinct in purpose, with clear resource-specific patterns like get_african_exchange_stocks vs get_ngx_all_stocks. Some overlap exists between generic African tools and NGX-specific convenience wrappers (e.g., get_market_open_status vs get_ngx_market_status), and get_african_policy_rates overlaps with get_country_macro_indicators on inflation/policy rate data, but descriptions clarify these boundaries.
All tools follow a consistent get_<domain>_<object> snake_case pattern, with plural/singular used appropriately (e.g., get_african_exchanges vs get_african_exchange). No mixed conventions or vague generic verbs—every name clearly signals its resource.
At 21 tools, the server is on the heavier side but within the 16-25 borderline zone. Each tool addresses a distinct data need for the broad African-markets domain, though some redundancy from NGX-specific wrappers (e.g., get_ngx_market_status vs get_market_open_status) could be trimmed.
The server covers a wide range of market data: exchanges, indices, stocks, FX, macro indicators, yield curves, and bank data. Minor gaps include lack of single-stock price/history for non-NGX exchanges and limited historical data beyond Nigeria's macro series, but core market-analysis workflows are well supported.
