Vike Data API

Token Screener

token_screener

Read-onlyIdempotent

Discover tokens by activity within a window. Rank by volume, net inflow, holder count, or smart-money inflow. Filters: min volume USD, min holders, smart-money-only. Use when the user asks 'what tokens are trending today' / 'find tokens with smart money accumulating' / 'rising tokens under $100M cap'.

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

Input Schema

Name	Required	Description	Default
`sort`	No	Sort metric (default volume)	volume
`chain`	No	Chain (default ethereum)	ethereum
`limit`	No	Max tokens (default 20, max 100)
`window`	No	Window (default 24h)	24h
`min_holders`	No	Filter tokens below this holder count
`min_volume_usd`	No	Filter tokens below this 24h volume
`smart_money_only`	No	Restrict to smart-money cohort flows. ethereum only: other chains (and sort=smart_inflow on them) are a 400

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4/5.0

Behavior3/5

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

Read-only, idempotent, non-destructive, and closed-world behavior are already declared in annotations, so the description's burden is low. It adds the notion of ranking and filtering but omits behavioral details such as result ordering ties, pagination/caps beyond the schema's limit, and the chain restriction on smart-money (which already lives in the parameter description).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all front-loaded: purpose, ranking options, filters, then usage triggers. No redundancy or filler, and the most decision-relevant information comes first.

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 7 optional parameters, full schema coverage, and annotations covering the safety profile, the description is sufficient to invoke the tool correctly. The only gap is that there is no output schema and the description does not hint at the shape of a returned token record, leaving the agent to infer it.

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% and each parameter already documents its enum values, defaults, and the smart-money 400 constraint, so the schema does the heavy lifting. The description restates the sort metrics and filters in prose but adds no syntax, units, or interaction rules beyond that baseline.

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?

States a specific verb and resource ('Discover tokens by activity within a window') plus the ranking dimensions and filter dimensions, which cleanly separates it from lookup tools like token_search or token_holders. An agent can tell this is a ranked discovery/screener tool 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 Guidelines4/5

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

Gives three concrete user-question triggers ('what tokens are trending today', 'smart money accumulating', 'rising tokens under $100M cap') that map well to intended use. It does not name an alternative tool or state when not to use it, so it falls short of a 5.

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

All Vike Data API 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.