Skip to main content
Glama
Sign In

Doti Protocol (.i) MCP Server

by io.github.robdomain
OverviewDiscussionsAdmin

transfer_domain

Prepare an unsigned ERC-721 transferFrom transaction payload to transfer sovereign ownership of a .i domain to another 0x EVM wallet address. Requires owner wallet signature.

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": {
      "domainName": "<domainName>",
      "currentOwner": "<currentOwner>",
      "newOwner": "<newOwner>"
    },
    "name": "transfer_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
newOwnerYesThe 0x recipient address to receive domain ownership
domainNameYesThe .i domain name to transfer
currentOwnerYesThe 0x address of the current domain owner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

In the absence of annotations, the description discloses the key behavioral fact that the tool prepares an unsigned payload rather than executing a transfer, and that a signature is required. However, it does not clarify the output format, whether ownership is verified, or what happens if the domain is not owned by the provided owner.

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?

The description is a single sentence with the core verb-object construction front-loaded: 'Prepare an unsigned ERC-721 transferFrom transaction payload.' The essential requirement ('Requires owner wallet signature') is appended without extraneous filler.

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?

Given no annotations and no output schema, the description covers the main purpose and prerequisite, but lacks important context such as the returned payload structure, whether the tool validates the current owner, and any network-specific considerations. It is adequate but not fully complete.

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?

The schema has 100% description coverage, with clear self-describing parameters (domainName, currentOwner, newOwner). The description adds no parameter-specific detail beyond the schema, but the baseline is 3 because the schema already sufficiently documents the parameters.

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 action ('prepare an unsigned ERC-721 transferFrom transaction payload') with a clear resource ('.i domain') and target recipient ('another 0x EVM wallet address'). This clearly distinguishes transfer_domain from sibling tools like bridge_domain, register_domain, and marketplace actions.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as bridge_domain or marketplace_buy_domain. The description mentions a prerequisite ('requires owner wallet signature') but does not explain the selection context or when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Doti Protocol (.i) MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources