Skip to main content
Glama

Emberlane Crypto Intelligence & Agent APIs

Multi-Chain EVM Token Security Preview

emberlane_scan_token_preview
Read-onlyIdempotent

Free quick safety score, honeypot flag, buy/sell tax, and DEX liquidity check for any ERC-20 token or smart contract on Base, BSC, Ethereum, Arbitrum, or Polygon.

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

Input Schema

NameRequiredDescriptionDefault
chainNoEVM network namebase
addressYes0x smart contract or token address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds behavior the annotations do not: that the call is free and fast, and which chains are covered. It omits whether results are cached, rate-limited, or how 'preview' degrades accuracy versus a full scan.

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?

A single front-loaded sentence that names the outputs, the asset type, and the chains with no filler. It is dense but readable; the only cost is that bundling four distinct checks and five networks into one clause makes it slightly harder to scan.

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 two-parameter read-only tool with full schema coverage, full annotations, and no output schema, the description covers what is checked, on which chains, and that it costs nothing. The remaining gap is what 'preview' limits relative to a full scan, which matters for an agent deciding whether these results are authoritative.

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% and the enum already enumerates the five chains, so the description's chain list largely repeats structured data. The address parameter is clarified as accepting either a token or a smart contract address, which is a genuine addition beyond the schema's '0x smart contract or token address' wording. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a concrete set of outputs (safety score, honeypot flag, buy/sell tax, DEX liquidity) plus the resource (ERC-20 token or smart contract) and the five supported chains. An agent can distinguish this from the sibling alpha/market-pulse tools, which cover different domains, though the description never names them. It stops short of a 5 because the 'preview' framing of the tool's purpose is left implicit.

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?

The words 'Free quick' imply a lightweight pre-check before deeper inspection, which is useful implied usage context. There is no explicit statement of when to use this versus another security or alpha tool, and no when-not conditions or prerequisites. Guidance is inferable but not stated.

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