Skip to main content
Glama
Sign In

Doti Protocol (.i) MCP Server

by io.github.robdomain
OverviewDiscussionsAdmin

resolve_domain_identity

Resolve a .i web3 domain name or 0x Ethereum wallet address to its sovereign identity, owner, metadata, social links, and current chain location.

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": {
      "identifier": "<identifier>"
    },
    "name": "resolve_domain_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoOptional filter for target network (42161: Arbitrum One, 10: Optimism, 1: Ethereum, 4663: Robinhood)
identifierYesThe .i domain name (e.g. "genesis.i") or EVM wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It lists the information returned and the optional chainId filter, but does not disclose potential side effects (e.g., that it is non-mutating, requires no authentication, or error behavior for invalid inputs). The word 'resolve' implies read-only, but explicit behavioral context is limited.

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?

A single, information-dense sentence with no superfluous words. The verb and primary resource are front-loaded, and the output list is concise. Every phrase contributes to understanding the tool's function.

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?

Given there is no output schema, the description compensates by explicitly listing the output categories (identity, owner, metadata, social links, chain location). It also notes the optional chainId filter. It omits details like response format or error handling, but for a straightforward resolver with only two parameters, the description is largely sufficient.

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 description coverage is 100%, so both parameters (identifier and chainId) are already documented. The description adds no additional semantic meaning beyond what the schema states, satisfying the baseline for adequate handling.

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 clearly states a specific verb ('Resolve') and resource ('.i web3 domain name or 0x Ethereum wallet address'), and enumerates the returned data categories (sovereign identity, owner, metadata, social links, chain location). This distinguishes it from sibling tools like register_domain or check_domain_availability, which have different purposes.

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 implies the use case: when you need detailed identity information for a domain or wallet. It does not explicitly name alternatives or state when not to use it, but the purpose is evident and clearly distinct from siblings, providing clear context without exclusions.

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