Skip to main content
Glama

Basename

basename

Base name lookup: a Basename (name.base.eth) to its address, owner and profile records, or an address to its forward-verified primary Basename. $0.001 per call over x402.

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": {
      "q": "<q>"
    },
    "name": "basename"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesa Basename (alice or alice.base.eth) or a 0x address
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.001 per-call x402 cost, states that reverse lookups return only a forward-verified primary name (a real correctness constraint), and enumerates what fields come back. It stops short of describing failure/empty behavior or whether payment is always required.

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?

One dense sentence covering both modes plus a short pricing sentence — front-loaded and waste-free. The pricing sentence is slightly bolted on but earns its place given the absence of annotations.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter lookup with no output schema, the description covers inputs, return shape, verification semantics, and cost/payment expectations. An agent has enough to call it and interpret the result without opening anything else.

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 parameters are already documented in the schema. The description reinforces the dual input form for q, but adds no syntax or edge-case detail beyond what the schema states; baseline 3 applies.

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?

The description names a specific resource (Basename / name.base.eth) and states both directions of resolution — name to address/owner/records and address to primary name. The 'Basename' framing implicitly distinguishes it from the sibling ens_resolve, but it never says so explicitly, so an agent must infer the difference.

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 two query modes are described, which implies when each input form applies, but there is no explicit when-to-use guidance, no mention of ens_resolve as the alternative for ENS names, and no note on what happens when no primary name exists.

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