Skip to main content
Glama

AgentHC Market Intelligence

get_economic_calendar

Economic event calendar with upcoming releases and data analysis.

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": "get_economic_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoResponse format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.full
include_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "full",
      +  "description": "Response format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.",
      +  "enum": [
      +    "full",
      +    "compact",
      +    "prompt",
      +    "agent"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about data freshness, time range coverage, whether results are paginated, or what 'data analysis' entails — the only content hint is 'upcoming releases', which is not enough for a no-annotation tool.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, but the brevity stems from under-specification rather than tightness; there is no front-loaded statement of what the call returns.

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?

With no annotations, no output schema, and an undocumented second parameter, the definition needed to do real work and instead offers one generic noun phrase. An agent cannot predict the response shape or when this tool beats its siblings.

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

Parameters2/5

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

Schema coverage is only 50%: the 'format' enum is documented in the schema, but 'include_prompt' has no description anywhere. The tool description adds no parameter meaning at all — 'data analysis' loosely gestures at the 'agent' format but never connects to either parameter.

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

Purpose3/5

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

The description names the resource (economic event calendar) and hints at contents (upcoming releases, data analysis), but uses no verb and never clarifies whether this lists events, returns analyzed data, or both. Nothing distinguishes it from siblings like get_market_snapshot or get_news_sentiment.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool for economic data versus snapshots or news. The agent is left to infer context entirely from the resource noun.

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.

Resources