Skip to main content
Glama
Sign In
DF Market Intelligence

DF Market Intelligence

by nasosal92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

macro_calendar

Retrieve upcoming US economic data releases—CPI, jobs reports, GDP—for the next N days to plan trading or research around scheduled market events.

Instructions

Economic release calendar — Upcoming US economic data releases (CPI, jobs report, GDP, etc.) for the next N days. Costs $0.005 USDC per call (x402 on Base), paid automatically from your configured wallet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "macro_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1-45, default 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the disclosure burden. It helpfully surfaces the payment model ($0.005 USDC per call, x402 on Base, auto-paid from wallet), which is genuine behavioral context. But it omits return shape, whether releases include dates/times/importance, and any timezone or coverage caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences with the purpose front-loaded before the cost note. Every clause carries information; the cost sentence is justified since no annotation conveys it.

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

Completeness3/5

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

For a simple one-param read tool this is mostly adequate, and the cost is disclosed. With no output schema and no annotations, though, the agent still cannot anticipate what a calendar entry contains or the format of returned dates/events.

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?

The single 'days' parameter is 100% covered by the schema ('1-45, default 14'). The description echoes 'next N days' but adds no constraint or format meaning beyond the schema, so baseline 3 applies.

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 gives a specific verb+resource: an 'economic release calendar' for 'upcoming US economic data releases' over 'the next N days', with concrete examples (CPI, jobs report, GDP). It's clearly distinct from a series/latest tool, though it never names the sibling (macro_latest/macro_series) to reinforce the distinction.

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?

Usage is implied by 'Upcoming ... for the next N days', which tells an agent this is the forward-looking view. However, no explicit when-to-use vs when-not, and the obvious alternatives (macro_latest, macro_series) are never referenced.

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

Deploy Server

Other Tools