Skip to main content
Glama

Lookup Address Label

lookup_label

Look up label and risk score for any cryptocurrency address. Returns entity name, category, risk flags, and compliance tags for due diligence.

Instructions

Look up the label and risk score for a cryptocurrency address. Returns entity name, category (exchange, DeFi, bridge, etc.), risk flags, and compliance tags. Cost: $0.009 per query. Source: On-chain address intelligence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesCrypto address to look up (e.g. 0xdAC17F958D2ee523a2206206994597C13D831ec7)

Implementation Reference

  • The async handler function that executes the 'lookup_label' tool logic. It calls apiGet on /api/v1/labels/{address}, handles 404 vs other errors, and returns the label data as JSON text.
      async ({ address }) => {
        const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
          `/api/v1/labels/${encodeURIComponent(address)}`,
        );
    
        if (!res.ok) {
          const msg =
            res.status === 404
              ? `No label found for address ${address}.`
              : `API error (${res.status}): ${JSON.stringify(res.data)}`;
          return {
            content: [{ type: "text" as const, text: msg }],
            isError: res.status !== 404,
          };
        }
    
        const warn = stalenessWarning(res);
        return {
          content: [
            { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
          ],
        };
      },
    );
  • Input schema for the lookup_label tool: requires a single 'address' string parameter describing the crypto address to look up.
    inputSchema: {
      address: z
        .string()
        .describe("Crypto address to look up (e.g. 0xdAC17F958D2ee523a2206206994597C13D831ec7)"),
    },
  • Registration of the 'lookup_label' tool via server.registerTool with its name, metadata (title, description), input schema, and handler function.
    server.registerTool(
      "lookup_label",
      {
        title: "Lookup Address Label",
        description:
          "Look up the label and risk score for a cryptocurrency address. Returns entity name, " +
          "category (exchange, DeFi, bridge, etc.), risk flags, and compliance tags. " +
          "Cost: $0.009 per query. Source: On-chain address intelligence.",
        inputSchema: {
          address: z
            .string()
            .describe("Crypto address to look up (e.g. 0xdAC17F958D2ee523a2206206994597C13D831ec7)"),
        },
      },
      async ({ address }) => {
        const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
          `/api/v1/labels/${encodeURIComponent(address)}`,
        );
    
        if (!res.ok) {
          const msg =
            res.status === 404
              ? `No label found for address ${address}.`
              : `API error (${res.status}): ${JSON.stringify(res.data)}`;
          return {
            content: [{ type: "text" as const, text: msg }],
            isError: res.status !== 404,
          };
        }
    
        const warn = stalenessWarning(res);
        return {
          content: [
            { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
          ],
        };
      },
    );
  • src/index.ts:23-23 (registration)
    Import of registerLabelTools from the labels module, necessary for the tool to be registered on the MCP server.
    import { registerLabelTools } from "./tools/labels.js";
  • src/index.ts:50-50 (registration)
    Registration call that invokes registerLabelTools(server), which internally registers the 'lookup_label' tool.
    registerLabelTools(server);
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions cost per query ($0.009) and source (on-chain intelligence), which are useful behavioral traits. However, it does not disclose rate limits, authentication requirements, or what happens if the address is not found.

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?

The description is extremely concise: two sentences plus cost and source. Every sentence adds value—purpose, return data, cost, and provenance. No wasted words.

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?

The description covers the tool's purpose, return data, cost, and source. It lacks mention of error handling or data freshness, but for a simple lookup tool with no output schema, it provides sufficient context for an AI agent to use correctly.

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% with one parameter (address) and its description. The tool description adds no additional meaning beyond what the schema already provides (e.g., example address). Baseline 3 is appropriate.

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 clearly states the verb 'look up', the resource 'cryptocurrency address', and the returned data (label, risk score, entity name, category, risk flags, compliance tags). It distinguishes itself from sibling tools like lookup_contract (smart contracts) and lookup_npi (medical providers) by specifying the domain.

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 description does not explicitly state when to use this tool versus alternatives like lookup_contract for contract addresses or lookup_whale for whale addresses. It only provides cost information and source, implying but not stating that it is specifically for address labels.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server