Insight Pre-Trade Safety

get_price_analytics

Run multi-oracle price analytics: consensus across providers, batch reads, historical series, cross-chain spreads, deviation, correlation or a risk summary. Use it when one price is not enough and the caller needs to compare, stress or trend oracle data. Do not use it for a single provider spot read (get_oracle_price) or for feed uptime (get_oracle_health). Returns the requested analysis rows plus provider participation and reference prices. Deprecated alias: prefer trade_guard with op "price_analytics". Removed on 2027-01-06.

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": {
      "assets": "<assets>"
    },
    "name": "get_price_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	End date YYYY-MM-DD
`from`	No	Start date YYYY-MM-DD
`mode`	No	consensus = cross-provider price, batch = multi-asset, history = time series	consensus
`chain`	No	Optional chain-name filter (e.g. "ethereum", "base", "hyperevm"); not a numeric chain id
`assets`	Yes	Assets to analyse; consensus/risk/history use the first asset
`method`	No	Consensus aggregation method
`metric`	No	Deep-analysis metric; overrides mode
`interval`	No	Deviation interval, default 24h
`provider`	No	Provider for history/spreads
`providers`	No	Required for metric=risk; otherwise uses the provider default
`base_chain`	No	Base chain name for metric=spreads
`period_hours`	No	Risk/history hours
`force_refresh`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / base_chain / description

Previous value: -"Base chain for metric=spreads"New value: +"Base chain name for metric=spreads"

changedInput schema / properties / chain / description

Previous value: -"Optional chain filter"New value: +"Optional chain-name filter (e.g. \"ethereum\", \"base\", \"hyperevm\"); not a numeric chain id"

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With zero annotations the description carries the full burden, and it does disclose the return shape ("requested analysis rows plus provider participation and reference prices") and lifecycle status (deprecated, removed 2027-01-06). It says nothing about permissions, rate limits, cost, or what happens on partial provider failure, which matters for a fan-out analytics call.

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?

Front-loaded with the core action and scoping, and the deprecation notice is short and unmissable. The opening enumeration of analysis types partly duplicates the schema's mode and metric enums, so a little of it is redundant rather than additive.

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?

For a 13-parameter, multi-mode tool with no output schema, the description covers purpose, routing, return values, and deprecation adequately, with the schema handling parameter detail. The only real gap is failure and permission behavior across multiple providers, which is left entirely implicit.

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 92%, so the baseline is 3 and the description does not beat it: it restates mode/metric value families without explaining precedence rules such as metric overriding mode or consensus/risk/history only using the first asset. Those rules live in the schema, so no value is added beyond it.

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?

"Run multi-oracle price analytics" gives a specific verb plus resource, and the following clause enumerates the concrete analysis families (consensus, batch, history, spreads, deviation, correlation, risk). It also names the siblings it is not (get_oracle_price, get_oracle_health), so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit positive condition ("when one price is not enough and the caller needs to compare, stress or trend oracle data") plus explicit exclusions naming the two better-suited siblings. It goes further and names trade_guard with op "price_analytics" as the preferred path, with a hard removal date, which is exactly the routing decision an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Insight Pre-Trade Safety tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.