FREE. Catalog of all afriref reference-data series: supported countries, series ids, descriptions, freshness metadata and per-series URLs. Call this first to discover what data exists.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It states it is 'FREE' and describes the output content but does not disclose potential performance, pagination, or rate limits. As a simple list tool, this is adequate but not fully transparent.
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 extremely concise: two sentences (22 words) with no wasted words. It front-loads key information ('FREE') and immediately conveys the tool's purpose.
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 no output schema and no annotations, the description adequately explains the tool's role and output contents. However, it could specify the output structure (e.g., array of objects) for greater completeness.
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 has no parameters, and the schema coverage is 100% (trivially). The description adds value by describing what the output contains, which compensates for the lack of parameters.
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 specifies the tool's function: listing all afriref reference-data series with details like supported countries, series IDs, descriptions, freshness metadata, and URLs. It uses specific nouns and distinguishes itself from sibling tools (e.g., get_series retrieves a specific series).
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?
Provides explicit guidance: 'Call this first to discover what data exists.' This implies it's the entry point before using other tools. While it doesn't list alternatives or exclusions, the context of sibling tools makes the usage clear.
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.
Each of the 11 tools addresses a clearly distinct operation: compliance checking, income tax, payroll, VAT, working days, holidays, series queries (current/history/snapshot/catalog), and settlement date. Even within the tax and calendar families, the descriptions precisely delineate boundaries, so there is no realistic risk of an agent selecting the wrong tool.
The vast majority of tools follow a consistent verb_noun snake_case pattern (check_, compute_, get_, list_, count_). The only deviation is settlement_date, which is a noun phrase rather than verb_noun, but it is still clear and idiomatic. This single outlier prevents a perfect score.
With 11 tools, the server is well-scoped for a reference-data domain covering statutory rates, calculations, calendars, and settlement conventions. Each tool has a distinct purpose and earns its place; the count is neither thin nor bloated.
The server provides strong coverage of its stated domain: statutory tax computations, payroll, minimum wage, VAT, holidays, working days, and settlement dates, plus a generic series API for extensibility. Minor gaps exist, such as payroll only supporting Nigeria and Kenya and no standalone social-security contributor, but the response descriptions explicitly disclose these limits, and the generic series endpoint provides a workaround for common lookups.
