List the jurisdictions and macro indicators (inflation, GDP growth) available to resolve_country_claim and get_country_indicator, with per-country year coverage and source. Call this to check coverage before resolving a claim or looking up an indicator.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the output content (jurisdictions, indicators, coverage, source) and purpose. It is a read-only listing with no side effects, though it does not explicitly state read-only or authentication needs; but with no annotations, this is sufficient.
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?
Two efficient sentences: first states purpose and output, second gives usage guidance. No wasted words, front-loaded with key information.
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, the description fully explains the return value (jurisdictions, indicators, coverage, source) and its use case relative to sibling tools. Completely adequate for a parameterless listing tool.
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 zero parameters and schema coverage is 100%, so baseline is 4. The description adds value by explaining 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 states it lists jurisdictions and macro indicators (inflation, GDP growth) available to specific sibling tools, with per-country year coverage and source. The verb 'list' is specific and the resource is well-defined, distinguishing it from siblings.
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?
Explicitly states 'Call this to check coverage before resolving a claim or looking up an indicator,' providing clear context on when to use the tool and its relation to related tools. No exclusions needed for a coverage check tool.
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 tool targets a distinct function: text analysis (detect_tensions, extract_assumptions), retrieval of published foresight (get_public_report, etc.), listing available resources (list_countries, list_public_spaces), searching (search_spaces), and macro claim resolution (resolve_country_claim). Even similar-sounding tools like detect_tensions and get_public_tensions are clearly differentiated by purpose (user-provided text vs. published analysis).
All tool names follow a consistent verb_noun pattern with underscores: detect_tensions, extract_assumptions, get_country_indicator, get_public_report, get_public_scenarios, get_public_tensions, list_countries, list_public_spaces, resolve_country_claim, search_spaces. The verbs are specific and the nouns are descriptive, making the naming predictable and easy to understand.
With 10 tools, the server covers its domain—strategic foresight and macro indicators—without being overwhelming. Each tool serves a clear purpose, and the count is appropriate for the scope: text analysis, resource listing, retrieval, search, and claim resolution. There is no unnecessary bloat or deficiency.
The tool set covers the core workflows: analyzing user-provided strategy text, retrieving published foresight reports/scenarios/tensions, listing available spaces and countries, searching, and resolving macro claims. A minor gap is the lack of a tool to retrieve a specific extracted assumption (though extraction is stateless by design). Overall, the surface is largely complete for a public-facing server.
