Skip to main content
Glama

Get ENS prices

get_price
Read-onlyIdempotent

Get the price to register or renew .eth names for a duration, e.g. 'How much is renewing nick.eth for 2 years?'. Prices are in USDC by default, or DAI; registration adds a temporary premium on recently expired names. Returns each name's price and the total.

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": {
      "names": "<names>",
      "duration": "<duration>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoregistration (default) or renewal
namesYes1 to 20 .eth names
durationYes
paymentTokenNoToken to pay with: usdc (default) or dai

Output Schema

NameRequiredDescriptionDefault
kindYes
itemsYes
totalYes
durationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: prices are denominated in USDC by default or DAI, and registration pricing includes a temporary premium for recently expired names — a non-obvious pricing rule an agent would otherwise miss.

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?

A single tight paragraph that front-loads the core action and then layers pricing caveats and the return shape. Every sentence carries information, with only mild density cost from combining example, currency, premium rule, and return note in one block.

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 an output schema present, the description need not detail return values, yet it still briefly summarizes them (per-name price plus total). For a read-only quote tool with 4 parameters including two enums, the definition supplies enough to call it correctly; only the duration string format and the registration/renewal distinction remain slightly underspecified.

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 75%, so the baseline is 3. The description reinforces the duration concept and the USDC/DAI token choice, and the example clarifies duration format ("2 years"), which the schema leaves as a bare string; but the registration-vs-renewal switch and the per-name batching semantics are only lightly touched rather than explained.

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 states a specific verb and resource: get the price to register or renew .eth names for a duration, backed by a concrete example query. It is clearly a pricing/quote tool rather than a state-changing one, though it never names siblings such as register_name or renew_names that an agent might otherwise reach for.

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 quoted example ("How much is renewing nick.eth for 2 years?") implicitly signals when to call this — cost-preview before a registration or renewal. However, there is no explicit when-not guidance and no named alternative for actually executing the registration or renewal, so the routing decision is left partly to inference.

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.