Get the latest price and trading history for a specific NGX-listed stock by ticker symbol (e.g. DANGCEM, GTCO, MTNN, ZENITHBANK, ACCESSCORP). Use this when the user asks about the price of a particular Nigerian stock.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | NGX ticker symbol (e.g. DANGCEM, GTCO, MTNN). Case-insensitive. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds that the tool returns 'latest price and trading history', which is some behavioral detail, but it doesn't disclose formatting, freshness, or potential limitations. Given the annotation coverage, the description provides moderate value beyond the structured data.
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 two sentences, front-loaded with the core action, and every sentence earns its place. It efficiently covers what, for whom, and when to use it without any fluff. This is a model of conciseness.
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 low complexity (one required parameter, read-only, no output schema), the description is complete enough. It specifies the input (ticker symbol) and the output (latest price and trading history), and the explicit usage context resolves ambiguity. The annotations fully cover safety, so no further behavioral disclosure is necessary.
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?
Schema description coverage is 100% for the single `symbol` parameter, which already includes examples and case-insensitivity. The description also mentions ticker examples, but this adds little beyond the schema. Since the schema already does the heavy lifting, 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 'Get the latest price and trading history for a specific NGX-listed stock by ticker symbol', using a specific verb and resource. It also distinguishes from sibling tools by emphasizing 'specific' stock, contrasting with broader tools like get_ngx_all_stocks or get_ngx_market_overview. Examples of tickers further clarify the intended use.
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 explicitly says 'Use this when the user asks about the price of a particular Nigerian stock.', providing clear context for when to invoke it. It does not explicitly name alternatives or exclusions, but the guidance is sufficient for a single-purpose tool. This matches the 'clear context, no exclusions' level.
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.
