Skip to main content
Glama
Sign In

Doti Protocol (.i) MCP Server

by io.github.robdomain
OverviewDiscussionsAdmin

marketplace_make_offer

Prepare an unsigned transaction payload to submit an offer in ETH to purchase any registered .i domain. Requires buyer 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>",
      "buyerAddress": "<buyerAddress>",
      "offerPriceInEth": "<offerPriceInEth>"
    },
    "name": "marketplace_make_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNameYesThe .i domain name to make an offer on
buyerAddressYesThe 0x buyer address making the offer
durationDaysNoValidity of offer in days (defaults to 7)
offerPriceInEthYesOffer amount in ETH (e.g. "0.02")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully discloses that the tool produces an unsigned payload and that the buyer must sign, which prevents an agent from assuming an on-chain transaction occurs. However, it does not explain what happens after signing, whether the offer is submitted immediately, or whether any listing state is required.

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 two short sentences with no filler. The core action and object are front-loaded, and the critical signing requirement is placed clearly in the second sentence.

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?

The description is minimally adequate for an agent to understand the tool's purpose and select it, and the schema documents all parameters. However, since there is no output schema, the return payload shape is not described, and the signing/submission flow is only hinted at. For a financial transaction-prep tool, this leaves meaningful ambiguity.

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%, and every parameter already has a meaningful description, including an ETH example for offerPriceInEth. The tool description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score of 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?

The description names a specific action — preparing an unsigned transaction payload — and a distinct resource: an ETH offer on a registered .i domain. It clearly distinguishes this from direct purchase (marketplace_buy_domain) and from accepting offers (marketplace_accept_offer).

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 intended use is implied: use this when making an offer on a .i domain rather than buying it directly. However, it does not explicitly contrast this tool with marketplace_buy_domain, marketplace_accept_offer, or marketplace_cancel_offer, nor does it state prerequisites or 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