Skip to main content
Glama
Sign In

chaink9

by com.chaink9
OverviewDiscussionsAdmin

scan-lite

Read-only

A quicker, cheaper ChainK9 check for bots that need a fast yes or no before buying a token on BNB Smart Chain, Ethereum, Base or Arc. It really buys and sells the token once on a fork of the chain, then reads the contract: honeypot, buy and sell tax, trade gas, ownership, owner functions in the bytecode, blacklist, proxy, liquidity and source checks. It skips /scan's extra trades and time-travel probes (taxes that change over time or after several sells, owner powers tried for real, transfer limits and cooldowns), so a recent full /scan is returned instead when one exists. The report's tier field says which ran. Lite results are stored, so /report returns them later too. Not charged when the address isn't a token or has no liquidity yet (422). Costs $0.005 per successful call in USDC on Base, Polygon, Arbitrum, Avalanche, BNB Smart Chain (USDT) or Solana, paid with x402 in the call's _meta; failed calls are free.

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": {
      "token": "<token>"
    },
    "name": "scan-lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobsc (BNB Smart Chain, the default), eth (Ethereum) or base (Base)
tokenYesToken address on the chosen chain

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?

Discloses behavior far beyond the annotations: it actually executes a buy and sell on a fork, lists exactly which contract checks run, explains the tier field distinguishing lite from full results, states results are cached and retrievable via /report, and specifies billing ($0.005 per successful call, failed calls free, no charge on 422). The readOnlyHint is accurate in that the buys/sells occur on a fork rather than live state, but the description's explicit disclosure of a per-call charge is important context the annotation alone would miss.

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 value proposition and the sibling differentiation, then cost and error terms. Dense and mostly waste-free, though the caching point is stated twice ('a recent full /scan is returned instead' and 'Lite results are stored, so /report returns them later') and could be one sentence.

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?

For a tool with no output schema and a non-trivial forked-execution behavior, the description covers the method, checks performed, caching semantics, the tier field in the response, error-code billing exception, and payment mechanism. An agent knows what it gets, what it costs, and when it is charged nothing.

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 100%, so the baseline is 3. The description does add the fact that Arc is a supported chain, which the chain parameter's own description omits (it lists only bsc, eth, base), but it adds no syntax or format detail for the token argument beyond the schema's pattern.

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?

Identifies a specific action and resource — a cheaper, faster token risk check (a forked buy/sell plus contract inspection) on four named chains — and explicitly positions it against /scan and scan-ultra by naming the probes it omits. An agent can distinguish it from every relevant sibling 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 Guidelines5/5

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

States the concrete use case ('fast yes or no before buying a token') and the condition that routes elsewhere ('skips /scan's extra trades and time-travel probes'), plus the fallback that a recent full /scan is returned instead when one exists. When-not guidance is implied by the same sentence that enumerates the skipped probes.

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

All chaink9 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