Market Intelligence MCP

Official

Overview Schema Source Related Servers Discussions Admin

search_indicators

Read-only

Need to find an economic indicator? Search by keyword to retrieve matching series including ID, name, frequency, and last updated date.

Instructions

Search for economic indicators by keyword. Returns matching series with ID, name, frequency, and last updated date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query (e.g., "unemployment rate", "consumer price index")
`limit`	No	Max results (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 25, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that it returns matching series with specific fields, but does not disclose pagination behavior or any constraints beyond the schema.

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?

The description is a single sentence that is front-loaded with the primary action and resource. Every word serves a purpose; no unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with two parameters and no output schema, the description adequately covers what the tool does and what it returns. Missing details like ordering or error handling are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description's mention of 'keyword' adds no new information beyond the schema description for 'query'. The limit parameter is similarly covered. Description does not enhance parameter understanding.

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?

The description clearly states the tool's purpose: 'Search for economic indicators by keyword' and specifies the return fields. This distinguishes it from sibling tools like 'economic_indicator' or 'employment_data' which likely target specific indicators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for keyword-based searching but does not provide explicit guidance on when to use this tool versus the many specific indicator tools (e.g., 'unemployment_data'). No exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.