Skip to main content
Glama
crypto-macro-pulse-mcp

crypto-macro-pulse-mcp

fetch_crypto_macro_intelligence

Fetch real-time crypto prices, USD forex rates (KRW/EUR/JPY), Fear & Greed sentiment, and asset news headlines in one call for crypto macro analysis.

Instructions

Fetch real-time crypto prices, USD forex rates (KRW, EUR, JPY), Fear & Greed Index, and financial news headlines.

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": {
      "coinIds": "<coinIds>"
    },
    "name": "fetch_crypto_macro_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinIdsYesCoinGecko asset IDs (e.g., ['bitcoin', 'ethereum', 'solana'])
maxNewsPerAssetNoMaximum news headlines per asset (1-10)
targetCurrenciesNoTarget fiat currency codes against USD (e.g., ['KRW', 'EUR', 'JPY'])
includeMarketNewsNoInclude latest financial news headlines per asset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it never mentions upstream rate limits (CoinGecko-style APIs are throttled), whether results are cached, what happens if the forex or news sub-fetch fails while prices succeed, or whether any authentication is required. "Real-time" is the only behavioral signal, and it is an unqualified claim rather than actionable context.

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?

A single front-loaded sentence with the verb first and the payload enumerated after — no filler, no redundancy. It is perhaps slightly too terse for a multi-source aggregator, but that is a completeness problem rather than a conciseness one.

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?

This is a composite tool that fans out to several external data sources, has no annotations and no output schema, yet the description says nothing about response shape, per-section failure handling, or rate-limit behavior. An agent cannot predict whether one missing news feed degrades the entire result. Given the tool's complexity, the definition is under-specified.

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 all four parameters (coinIds, maxNewsPerAsset, targetCurrencies, includeMarketNews) are already documented inline with defaults and ranges. The description adds only a light restatement by naming KRW/EUR/JPY and news headlines, which mirrors the defaults rather than explaining semantics. Baseline 3 is appropriate here.

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 opens with a specific verb ("Fetch") and enumerates exactly what comes back: crypto prices, USD forex rates, Fear & Greed Index, and news headlines. This meaningfully expands on the vague title phrase "macro intelligence." It loses a point only because there are no sibling tools to differentiate against and no statement of scope limits.

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 at all — nothing says which tasks should pick this tool, what prerequisites exist, or when a narrower tool would be preferable. The single word "real-time" hints at freshness but offers no exclusion criteria or call-frequency guidance for an aggregator that hits multiple upstream APIs.

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