Skip to main content
Glama

news propagation

news-propagation
Read-onlyIdempotent

Does news about coin X move Y? Measured 30-day hourly return correlation anchor vs related perps (not narrative: ETH->LINK strong, NVDA->RENDER weak) -> PROPAGATES/ISOLATED + per-link strength Price: $0.05 per call, USDC on Base via x402.

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": {
      "anchor": "<anchor>"
    },
    "name": "news-propagation"
  }
}

Input Schema

NameRequiredDescriptionDefault
anchorYesstring, e.g. ETH|BTC|SOL|NVDA or any perp ticker
candidatesNooptional list of tickers to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description's job is to add what they cannot: it discloses the measurement window (30-day hourly returns), the output shape (PROPAGATES/ISOLATED plus per-link strength), and the payment/auth model ($0.05 per call, USDC on Base via x402). The 402 payment requirement is exactly the kind of operational context annotations cannot convey.

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?

The core question is front-loaded and no sentence is wasted, but the telegraphic style with arrow notation and the pricing clause tacked onto the end makes it denser than it needs to be. It reads efficiently but slightly at the cost of parseability.

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

Completeness4/5

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

With no output schema, the description steps in to describe the return shape, and it also covers cost and payment rail. The main remaining gap is default behavior when candidates is not supplied, which matters for a tool whose second parameter is optional.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it establishes anchor as the news-source asset and candidates as the related perps being tested, and the ETH->LINK / NVDA->RENDER examples clarify what a plausible pairing looks like. It still does not say what happens when candidates is omitted.

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 names a specific measurement (30-day hourly return correlation between an anchor and related perps) and a concrete output verdict (PROPAGATES/ISOLATED), so the resource and operation are clear. It does not explicitly contrast itself with any sibling tool, relying instead on the internal 'not narrative' clarification to distinguish its methodology.

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 opening question 'Does news about coin X move Y?', which signals a lead-lag/contagion investigation but never states when to pick this over siblings like harmony-grade or ticker-collision. No exclusions or prerequisites are given beyond the cost line.

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