Market Intelligence MCP

Official

Overview Schema Source Related Servers Discussions Admin

economic_indicator

Read-only

Fetch time series data for any economic indicator by series ID (e.g., GDP, UNRATE). Returns date-value pairs for macro analysis.

Instructions

Get time series data for any economic indicator by series ID (e.g., GDP, UNRATE, CPIAUCSL). Returns date-value pairs.

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": {
      "series_id": "<series_id>"
    },
    "name": "economic_indicator"
  }
}

Input Schema

Name	Required	Description
`series_id`	Yes	Economic indicator series ID (e.g., GDP, UNRATE, CPIAUCSL, DFF)
`limit`	No	Number of observations to return (default 10)
`start_date`	No	Start date (YYYY-MM-DD)
`units`	No	Data transformation: lin (levels), pch (% change), pc1 (YoY % change)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 25, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that it returns 'date-value pairs', providing clarity on output format. No contradictions.

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 with no wasted words, efficiently stating purpose and output.

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

Completeness2/5

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

While the description covers core functionality, it lacks context for handling the many sibling tools. No explanation of output structure beyond 'date-value pairs' despite no output schema.

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%, so the description adds minimal value for parameters. It mentions series IDs with examples, but these are also in the schema. The 'date-value pairs' part is about output, not parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves time series data for economic indicators by series ID, with examples. However, it does not differentiate from sibling tools like employment_data or inflation_data, which are specific but also return time series.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools, agents need explicit context to choose correctly.

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