Skip to main content
Glama

zato crypto data

Basename/ENS lookup both ways: name -> address, address -> primary name (Base and Ethereum)

name_resolve
Read-only

ENS/Basename lookup both ways: name -> address, or address -> primary name. Price: $0.002 USDC per call (x402, Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "name_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname to resolve, e.g. jesse.base.eth
addressNoor an address for reverse lookup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds non-obvious operational context beyond them: payment of $0.002 USDC per call via x402 on Base, which matters for an agent deciding whether to invoke. It stops short of disclosing resolution failure behavior or which chain a resolution occurs on.

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?

Two short sentences with zero filler: the capability is front-loaded and the pricing follows. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should pin down what comes back (resolved address vs. primary name, and what happens on no-resolution) and the both-params-supplied case; it does neither. Pricing and bidirectional scope are covered, so the core is present, but gaps remain for a two-mode lookup tool.

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 description coverage is 100% and both parameters carry inline descriptions with an example, so the baseline is 3. The description reinforces that the two parameters are alternate modes, but adds no detail on mutual exclusivity, conflicting inputs, or accepted address/name formats beyond 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 states a specific verb+resource in both directions: 'ENS/Basename lookup both ways: name -> address, or address -> primary name.' This is far more precise than the terse title and lets an agent distinguish it from siblings like dns or payto_check without opening a schema.

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 makes the two usage modes (forward vs reverse lookup) explicit, which is genuine when-to-use guidance for choosing a mode. It gives no guidance on prerequisites, on what happens if both or neither parameter is supplied, or on when to prefer a sibling tool, so it stays at implied usage rather than explicit routing.

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