Skip to main content
Glama

registry_lookup

Read-onlyIdempotent

Look up a contract address in the Known Contract Label Registry. Returns protocol name, category, risk level, and tags. Free — no payment required.

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

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain network (e.g., ethereum, base)
addressYesContract address (0x-prefixed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description usefully adds the return shape (since no output schema exists) and the notable pricing fact ('Free — no payment required'), which matters in a catalog where paid tools exist. It omits what happens on a miss and how complete the registry's coverage is.

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?

Three short sentences with the resource and return values front-loaded; nothing is wasted. The 'Free — no payment required' clause is slightly redundant with itself but carries real signal for tool selection.

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 read tool with rich annotations, the description covers what it does, what it returns, and its cost. The remaining gap is chain scoping versus the Solana sibling and not-found behavior, which are meaningful but not blocking for correct invocation.

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 both 'address' and 'chain' are already documented with examples in the schema. The description adds no parameter-level meaning beyond that — notably it never says whether 'chain' is required for disambiguation or defaults to a particular network.

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?

States a specific verb and resource ('Look up a contract address in the Known Contract Label Registry') and enumerates the returned fields (protocol name, category, risk level, tags). It does not differentiate from the obviously adjacent sibling solana_program_lookup, so an agent cannot tell from the text alone which registry applies to which chain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Usage is only implied by the verb 'look up' — there is no explicit statement of when to use this versus address_check, contract_docs, or solana_program_lookup. No exclusions, prerequisites, or fallback behavior are given if the address is absent from the registry.

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.