list_indicators
List the indicators this server supports (World Bank + US BLS), with descriptions. Call this to discover what you can query.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
economy-intel-mcp
by com.datakoot
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes output (indicators with descriptions) but no additional behavioral details like pagination or format. Acceptable for a simple list tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences covering action and usage. Front-loaded, no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Fully adequate for a simple discovery tool with no params and no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; baseline for zero-param tools. Description adds value by naming data sources.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it lists supported indicators from World Bank and US BLS with descriptions. Distinguishes itself from sibling tools which focus on specific queries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to call this to discover what can be queried, providing clear context for use. No exclusions but sufficient for discovery.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool has a distinct query shape: cross-country single-indicator comparison, single-country time series, single-country snapshot, indicator discovery, and US BLS time series. The descriptions clearly mark these boundaries, so an agent is unlikely to confuse them.
Naming Consistency4/5
All tool names use lowercase snake_case and are readable, but they mix verb-led names like compare_countries and list_indicators with noun-led names like country_indicator and us_series. This is a minor inconsistency rather than a chaotic or unpredictable pattern.
Tool Count5/5
Five tools is well-scoped for a read-only economic data server. Each tool covers a unique, necessary capability: discovery, single-country indicator history, country snapshots, cross-country comparison, and US BLS data.
Completeness4/5
Core workflows are covered well: discover indicators, fetch country-level macro data, profile a country, compare countries, and access US series. A minor gap is that cross-country historical comparisons are not directly supported and would require composing multiple country_indicator calls.