Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

market_convergence_index

[$0.25] Cross-correlate 48h multi-source social and news momentum with institutional SEC filings and on-chain capital flow signals to separate organic adoption from retail noise.

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

Input Schema

NameRequiredDescriptionDefault
seedNoSector, asset identifier, or keyword seed (e.g. 'USDC', 'AI agents', 'NVDA')
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the price ($0.25) and the fixed 48h lookback window, but says nothing about permissions, rate limits, data freshness/latency, or what the correlated output actually looks like (no output schema exists). For a paid, multi-source correlation tool with zero annotation coverage, the disclosure is thin.

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?

It is a single dense sentence with the cost front-loaded in brackets and the analytical payoff at the end. Nothing is redundant, though the phrasing is jargon-heavy and could be split for faster scanning.

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 two-parameter but behaviorally complex aggregation tool with no annotations and no output schema, the description covers inputs and data sources but not the return shape, scoring method, or failure modes beyond what the schema says about timeout. Adequate to decide whether to call it, incomplete for predicting what comes back.

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 description coverage is 100%, so both the 'seed' and 'timeout_ms' parameters are already documented in the schema, and the baseline of 3 applies. The description adds a little context by implying the seed drives which social/news/filing/on-chain sources are correlated, but it does not clarify seed syntax, granularity, or how the optional timeout interacts with the degraded response.

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 uses a specific verb ('Cross-correlate') and enumerates the exact signal classes it fuses: 48h social/news momentum, institutional SEC filings, and on-chain capital flow. It also states the analytical goal ('separate organic adoption from retail noise'), so an agent knows this is a synthesis/scoring tool rather than raw retrieval. It stops short of naming which sibling (e.g. research_bundle, topic_briefing, trends) it replaces, so sibling differentiation is left implicit.

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 only implied through the framing about separating organic adoption from retail noise, which suggests a due-diligence or signal-validation scenario. There is no explicit when-to-use, no when-not-to-use, and no pointer to alternative tools for simpler lookups. An agent can guess the fit but is not routed.

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