Skip to main content
Glama
Sign In

LayerHop

by com.layerhop
OverviewDiscussionsAdmin

Look up a token by address

lookup_token
Read-only

Get one token's symbol, name, decimals, USD price and verified flag from its contract address or SPL mint. The chain is optional: LayerHop finds it (Solana for a mint, else the EVM chain where the token has the most liquidity). verified false means it is on no curated list: confirm the address with the user before swapping. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
chainNoOptional: the token's chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
addressYesToken contract address (EVM 0x...) or SPL mint (Solana).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is read-only and open-world, so the bar is lower. The description adds meaningful behavior beyond that: automatic chain resolution, the Solana-mint special case, the max-liquidity EVM fallback, and the meaning and safety implication of verified=false.

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?

The description is front-loaded, dense, and mostly free of waste. The final 'Read-only' sentence is redundant with readOnlyHint=true, but the rest of the wording earns its place.

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 simple two-parameter lookup with no output schema, the description is nearly complete: it enumerates the returned fields and explains the optional-chain behavior. It could be stronger by mentioning invalid-address or chain-mismatch behavior, but nothing essential is missing for normal use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds value beyond the schema by explaining how an omitted chain is resolved and by reinforcing that address may be an EVM contract or Solana SPL mint.

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?

The description states a specific verb and resource: get one token's symbol, name, decimals, price, and verified flag from an address or SPL mint. The 'one token' framing distinguishes it from list-oriented siblings such as list_tokens, and the returned fields distinguish it from risk or transaction tools.

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?

It gives useful calling context by explaining that chain is optional and how LayerHop resolves it, plus a safety rule when verified is false. However, it does not explicitly say when to choose this over siblings like get_token_risk or list_tokens, nor when it should not be used.

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

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