Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Token Search

token_search
Read-onlyIdempotent

Search for tokens by name or symbol. Returns matching symbols, names, addresses (0x-prefixed, lower case; pass them straight to token_holders and token_transfers), and logos.

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": {
      "query": "<query>"
    },
    "name": "token_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain. Default: ethereumethereum
limitNoMax results (default 10)
queryYesSearch term (symbol or name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/closed-world, so safety is covered. The description adds genuinely non-obvious behavior: exactly what comes back (symbol, name, address, logo) and the address normalization contract (0x-prefixed, lowercase, directly passable), which prevents an agent from mangling casing before chaining calls.

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?

Two sentences, front-loaded with the operation and followed by the return contract. Every clause earns its place, particularly the address-format and handoff detail.

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?

There is no output schema, so the description carries the return-value burden and discharges it by enumerating the returned fields and the address format. Combined with the 100%-covered input schema and read-only annotations, an agent has everything it needs to call and chain this tool.

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%, with the chain enum and limit default fully documented in the schema, so the baseline applies. The description adds no extra meaning about query matching semantics (prefix vs substring, case sensitivity) or how chain restricts the result set.

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 ('Search for tokens by name or symbol') and immediately scopes it against downstream siblings by saying the returned addresses go straight to token_holders and token_transfers. An agent can distinguish it from token_screener (metric-based screening) and the address-keyed tools without opening a 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?

Implies the use case clearly: resolve a name or symbol into a chain address you can then feed to token_holders/token_transfers. It names the successor tools explicitly but gives no when-not-to-use guidance (e.g., vs token_screener) and no note that results are chain-scoped.

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 toolsInspect
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.

Resources