Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_ohlcv

nansen_token_ohlcv
Read-onlyIdempotent

OHLCV price candles for a token (1m to 1M). Use a coarse timeframe for long windows to keep output small. 1 credit.

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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "nansen_token_ohlcv"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 7). Ignored when date_from is set.
chainYes
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
timeframeNoCandle size (default 1h)
token_addressYesToken contract address (use nansen_search to resolve a symbol first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world. The description adds two non-obvious facts the annotations cannot convey: a cost of 1 credit and a size-management warning about timeframe/window combinations. It stops short of stating any cap on returned candles or pagination behavior.

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?

Three short, front-loaded sentences with no filler; the resource is stated first and the practical constraints follow. The '1m' value is a small accuracy blemish but not wasted prose.

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 six-parameter read tool with no output schema, annotations covering safety, and high schema coverage, this covers purpose, cost, and the main output-size pitfall. An agent could call it correctly; only the candle payload shape and any result limits remain unstated.

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 83%, so the schema already explains days, date_from/date_to precedence, and timeframe defaults. The description only echoes the timeframe range, and that echo is imprecise relative to the enum. Baseline 3 is appropriate.

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?

States a specific verb+resource: OHLCV price candles for a token, which distinguishes it from sibling token tools covering trades, flows, and holders. Minor flaw: the stated range '1m to 1M' does not match the schema enum, which starts at 5m, and no sibling is named explicitly.

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?

Gives one actionable usage rule — pick a coarse timeframe for long windows to keep output small — which implies the tool is for trend/series analysis rather than trade-level inspection. However, it never says when to use this versus nansen_token_dex_trades or nansen_token_indicators, and offers no exclusions.

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