Skip to main content
Glama

Token risk check

check_token
Read-onlyIdempotent

Zorvu's automated risk check on any Robinhood Chain token: the grade, each check that ran with its result and reason, a drainer-code check, and when every underlying reading was taken.

Call this on any token address before you interact with it, and whenever a user names a token you have not checked. For a whole transaction, use precheck_transaction instead: it decodes the calldata and checks the spender as well.

The drainer-code check and the official Stock Token lookalike check (on the token's live symbol() and name()) run live. Zorvu's other token measurements (liquidity, holders, sell test, deployer history) are archived readings: an archived reading never counts as a pass, may support a warn or a fail for 7 days with its date in reading_at, and is not used after that. token_data says which applies (archived or none). The grade says what those checks measured at the time shown; it never means the token is safe or safe to buy, and it is not a recommendation. While Zorvu's token measurements are an archive the grade is Not yet checked, Limited data, Elevated risk, High risk, or Not applicable for a base asset of the chain. It is never Low risk today, so passed_zorvu_safety_checks is false on every answer: treat it as no signal rather than as a token having failed. A check Zorvu could not run is no_data or inconclusive, never a pass. These are measurements, not advice; they may be incomplete, wrong or out of date. Not financial advice.

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": {
      "address": "<address>"
    },
    "name": "check_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract address on Robinhood Chain.

Output Schema

NameRequiredDescriptionDefault
chainNo
gradeYesWhat Zorvu's automated checks measured: Not applicable, Not yet checked, Limited data, Elevated risk or High risk. Never Low risk while the token measurements are an archive, because an archived reading never counts as a pass.
notesNo
statsNo
checksYes
symbolNo
addressYes
archiveNo
disputeNo
freshnessYes
disclaimerYes
token_dataNo
api_versionYes
drainer_checkNo
in_zorvu_dataNo
ticker_sourceNo
checked_factorsNo
passed_zorvu_safety_checksYestrue only when the grade is Low risk, so false on every answer while the token measurements are an archive. Not the same field as the one on each entry of precheck_transaction’s tokens[], which has its own rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety/idempotency; the description goes far beyond them, disclosing which checks run live versus archived, the 7-day validity window on archived readings, the `token_data` marker, the fact that `passed_zorvu_safety_checks` is always false and should be read as no signal, and that `no_data`/`inconclusive` never count as a pass. That is exactly the non-obvious behavior an agent would otherwise get wrong.

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?

Well front-loaded: purpose, then when-to-use and the alternative, then the archive semantics and caveats. It is long, and the non-advice disclaimer is restated twice ('not a recommendation' then 'These are measurements, not advice. Not financial advice'), which is the main redundancy.

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?

An output schema exists, so return shape needn't be spelled out, yet the description still explains how to interpret the grade and `token_data` — the parts a schema cannot convey. For a read-only single-address check, nothing an agent needs to call it or interpret the answer is missing.

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?

One required parameter with 100% schema coverage, so the schema already documents the address pattern and meaning; baseline 3 applies. The description adds only mild context (the token must be on Robinhood Chain, and `symbol()`/`name()` are read live for the lookalike check), not format or edge-case detail.

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 — an automated risk check on a Robinhood Chain token — and enumerates what comes back (grade, per-check result and reason, drainer-code check, reading timestamps). It explicitly carves out the sibling: `precheck_transaction` is for whole transactions and adds calldata decoding and spender checks.

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?

Gives an explicit trigger ('call this on any token address before you interact with it, and whenever a user names a token you have not checked') and an explicit alternative with the condition that selects it ('for a whole transaction, use precheck_transaction instead'). No inference required.

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