Skip to main content
Glama
Sign In

AskHook

by fun.askhook
OverviewDiscussionsAdmin

Look up a token

lookup_token
Read-only

Resolve a token symbol or address on Elysium to its address, symbol and decimals, verified on-chain. HYPE is native.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesSymbol (HYPE, WHYPE, USDC, ASKHOOK...) or 0x address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already establish read-only and open-world behavior. The description contributes the phrase 'verified on-chain', which hints that resolution is validated against the chain and may therefore fail, plus the native-token caveat, but it does not say what happens when a token is unverified, unknown or ambiguous between the two accepted input forms. With annotations carrying the safety profile, a 3 is appropriate.

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?

It is a single tight sentence, front-loaded with the verb and the resolution target, followed by the return fields and then the HYPE caveat. There is no filler or redundant restatement of the title.

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?

With no output schema, the description fills that gap by naming the returned fields (address, symbol, decimals). For a one-parameter lookup tool that is nearly complete; the remaining gap is the error or not-found behavior, which the description does not address.

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 parameter is already documented. The description still adds semantic value by noting 'HYPE is native', a special case the schema's example list does not explain, and by tying the accepted input forms to a specific chain (Elysium). This meaningfully supplements rather than repeats the schema.

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 uses a specific verb ('Resolve') with a named resource (a token symbol or address on Elysium) and states exactly what comes back: address, symbol and decimals. That is enough to distinguish it immediately from the hook-oriented siblings, which all deal with hooks, pools and templates rather than token metadata.

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?

Usage is only implied: an agent must infer that this tool is for converting a symbol or 0x address into canonical token metadata. There is no explicit when-to-use statement, no exclusion such as 'do not use for pricing', and no mention of alternatives. The one-line scope is clear but the guidance is inferential rather than stated.

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

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