Skip to main content
Glama

agent-exec

Rent a name under 448c.net (paid, x402)

dns_rent

PAID: rent a DNS name, .448c.net, for a year with A/AAAA/CNAME/TXT records; the paying wallet owns it. 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_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoThe label to rent, without the zone: it becomes <label>.448c.net. Lowercase letters, digits and hyphens; some labels are ours and refused.
dryRunNoOptional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.
recordsNoWhat the name resolves to. The route states the record and TTL limits in details.expected on any refusal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds the price ($0.5000 USDC), the accepted chains and asset, the fact that even a dry run is billed, that reserved labels are rejected, and that the paying wallet takes ownership. It also discloses that the feedback channel is free and read daily with no individual reply, which is behavior an agent could not infer from structured fields.

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?

Front-loaded with the paid nature and the core action, then the payment mechanics, then the price. It is dense but each clause carries information, though the feedback-channel sentence is tangential to invoking the tool and could be dropped.

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?

For a paid mutation tool with no output schema, the description covers the payment handshake, the refusal behavior (details.expected in the route/schema) and the ownership effect. The success response shape is only hinted at via the schema's dryRun wording, which is a minor residual gap.

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 label, dryRun and records are already documented in detail, including the paid nature of dryRun and the TTL range reference. The description adds essentially nothing beyond that, so baseline 3 applies.

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?

Names a specific verb and resource ('rent a DNS name, <label>.448c.net, for a year') plus the record types allowed and the ownership outcome ('the paying wallet owns it'). An agent can tell this apart from a renewal tool because the one-year term and the rental framing are stated outright.

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?

The description spells out the two-step payment protocol: call unpaid to get the price, then resubmit with the x402 payment in _meta and call again. It also flags that some labels are reserved and refused. It stops short of stating when to prefer a sibling such as dns_renew for an existing name, so it is clear context without explicit alternatives.

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.