Skip to main content
Glama

Price impact

get_impact
Read-only

Standard and Pro: how a coin's price moved around past stories. Each recorded story is one real event, timed at its earliest report across outlets and languages; its coins' prices were recorded just before publication and 15 minutes, 1, 4 and 24 hours after, with BTC alongside. Give coin, or story for one story's coins. Filter with category, genre, kind (the story's calendar entry kind), direction (bullish or bearish news, from the story's sentiment score) and min_prominence (0-1); from/to (YYYY-MM-DD, both included, at most 366 days) default to the last 90 days, and Standard reaches 90 days back. summary covers every match up to 2,000 (total counts them; truncated, beside total, says the answer was cut, and scanned_from says how far back it is complete): per horizon n, median, p25, p75, up_share and median_vs_btc, in percent, with n alone when fewer than 5 samples. before_1h is the move over the hour before publication, so you can see how much of a move came first. events (limit default 20, max 100) list the stories newest first with price_at, change and vs_btc (percent from price_at; vs_btc is the coin's change minus BTC's), source, price_basis (candle: the close of a one-minute exchange candle; sample: a CoinGecko price sampled about every five minutes) and complete (false while later checkpoints are still due). Past observations with sample sizes, not a forecast. Cite stories by id or reader_url.

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_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
coinNo
fromNo
kindNo
genreNo
limitNo
storyNo
categoryNo
directionNo
min_prominenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description explains the data collection method, timing checkpoints, minimum sample threshold, truncation behavior, event completeness, price basis, and the difference between candle and sampled prices. It also clarifies that results are past observations rather than forecasts, which is important behavioral 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?

The definition is information-dense and front-loads the core purpose before moving into parameters and output details. It is long and packed into a single block, but most clauses carry useful operational meaning for a complex tool.

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

Completeness5/5

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

For a complex 10-parameter analytical tool with no output schema, the description supplies the missing return structure, includes summary and event fields, explains truncation and completeness, and covers date/count defaults. It gives enough detail for an agent to interpret and invoke the tool correctly.

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?

With zero schema description coverage across 10 parameters, the description compensates well by explaining coin, story, date defaults and limits, direction, kind, min_prominence range, and limit defaults. The remaining gap is that min_prominence's underlying meaning and some enum dimensions such as genre and category are not elaborated beyond their labels.

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

Purpose5/5

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

The description states a specific resource and analytical action: how a coin's price moved around past stories, including exact measurement horizons. It also distinguishes coin-scoped from story-scoped use, so an agent can understand the tool's purpose without opening the schema.

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?

The description gives invocation guidance such as providing coin or story, available filters, date defaults, and the Standard plan's 90-day limit. However, it does not explicitly say when to use this tool instead of siblings like get_market, get_coin, or get_story.

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.