Skip to main content
Glama

Extend a rented name (paid, x402)

dns_renew

PAID: extend a DNS name you own by a year. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.5000 USDC.

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

Input Schema

NameRequiredDescriptionDefault
nameNoThe full rented name, as returned when it was rented, e.g. example.448c.net.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive, closed-world mutation; the description adds substantial context beyond that — the x402 payment protocol, the exact _meta key, seven supported chains, and the exact price ($0.5000 USDC). It leaves out renewal edge cases (expired names, repeat renewal, failure/refund behavior), which keeps it from a 5.

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?

The payment requirement and action are correctly front-loaded, and the payment instructions are compact. The trailing 'Feedback: POST /feedback (free). Read daily; no individual reply.' is largely irrelevant to invoking this tool and dilutes the payload.

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 one simple parameter, no output schema, and annotations covering the safety profile, the description supplies what matters: price discovery on the unpaid call, the payment mechanism, and supported chains. Remaining gaps are edge-case behavior for renewing expired or already-extended names.

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?

There is a single 'name' parameter with 100% schema description coverage, including an example value, so the schema already carries the semantics. The description only echoes the idea of a name you own and adds no format or validation detail 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 opening clause 'PAID: extend a DNS name you own by a year' gives a specific verb (extend), resource (DNS name), and effect (one year), and 'you own' implicitly separates it from dns_rent for new names. An agent can identify the operation without consulting the schema.

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

Usage Guidelines4/5

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

It clearly states the two-step workflow: call unpaid to get the price, pay via _meta['x402/payment'], then call again. This is real when/how guidance for invocation, though it does not explicitly contrast with the dns_rent sibling or state what happens for an expired or non-owned name.

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