@namemyapp/mcp

buy_link

Generate a one-click purchase URL for a domain, letting the user complete the purchase directly on namemy.app.

Instructions

Build a one-click purchase URL the user can open to buy a domain on namemy.app. Always available (works without an API key). Use this when the user has decided on a name they like — hand them the URL and they sign up + pay in their browser.

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": {
      "domain": "<domain>"
    },
    "name": "buy_link"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Fully-qualified domain to buy, e.g. 'codeflow.ai'
`priceUsd`	No	Optional quoted price in USD. If omitted, the checkout page will fetch the live price.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.5Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Despite having no annotations, the description discloses key behavioral traits: always available without API key, generates a URL for browser-based purchase, and does not execute the purchase itself. This adds useful context beyond the schema, though it does not cover potential error conditions or edge cases.

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?

Two sentences, front-loaded with the primary purpose, followed by usage guidance. Every word earns its place with no redundancy or tangents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter URL builder with no output schema, the description fully covers its purpose, usage context, and non-obvious behavioral aspect (no API key required). The agent has enough to invoke the tool correctly.

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 the schema already fully documents domain and priceUsd. The tool description adds no additional parameter-level detail, resulting in a baseline score of 3.

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 the tool builds a one-click purchase URL for buying a domain, with a specific verb and resource. It also differentiates from the sibling tool buy_domain by explaining that the user completes payment in their browser, not via API.

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?

Explicitly says 'Use this when the user has decided on a name they like' and describes the hand-off flow. It does not explicitly name alternatives or state when not to use, but the context is clear enough for an agent to decide.

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

Deploy Server

Other Tools

buy_linkA