Skip to main content
Glama

namemyapp

by io.github.Rakesh1002
OverviewDiscussionsAdmin

Buy a domain

buy_domain
Destructive

Purchase a domain using the stored payment method. Returns success/failure. Pass connect to also point it at a deployment (Vercel, Netlify, Cloudflare Pages, GitHub Pages, Render, Railway, Fly) in the same call. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]

Input Schema

NameRequiredDescriptionDefault
yearsNoRegistration years. Omit to use the registry minimum (1 year; .ai is 2 years, charged at purchase).
domainYesDomain to purchase
connectNoOptional: after the purchase succeeds, point the domain at this deployment (same as connect_domain). It is validated before anything is bought; its result is reported under `connect`, and a connect failure does not undo the purchase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / connect
      Added value: +{
+  "description": "Optional: after the purchase succeeds, point the domain at this deployment (same as connect_domain). It is validated before anything is bought; its result is reported under `connect`, and a connect failure does not undo the purchase.",
+  "properties": {
+    "includeWww": {
+      "default": true,
+      "type": "boolean"
+    },
+    "target": {
+      "enum": [
+        "vercel",
+        "netlify",
+        "cloudflare-pages",
+        "github-pages",
+        "render",
+        "railway",
+        "fly"
+      ],
+      "type": "string"
+    },
+    "value": {
+      "description": "The platform's hostname for the deployment: my-site.netlify.app, my-app.pages.dev, octocat.github.io, my-app.onrender.com, the *.up.railway.app target Railway shows after you add the domain there, or the my-app.fly.dev hostname / public IP from `fly certs setup`. Optional for vercel (only if its dashboard shows a *.vercel-dns*.com CNAME for www).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "target"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / properties / years / default
      Removed value: -1
    • changedInput schema / properties / years / description
      Previous value: -"Registration years"New value: +"Registration years. Omit to use the registry minimum (1 year; .ai is 2 years, charged at purchase)."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructive and open-world behavior, so the bar is lower, yet the description adds genuinely useful traits: purchase is charged to a stored payment method, connect is validated before anything is bought, and a connect failure does not roll back the purchase. It does not state refund/reversibility of the purchase itself, which for a destructiveHint=true transaction would be worth knowing.

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?

Three front-loaded sentences: primary action first, then the optional combined path, then the prerequisite API key. Dense but every clause carries information; the bracketed API-key note is slight clutter but operationally necessary.

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 nested-object, no-output-schema tool, the description covers the purchase outcome ('success/failure'), the atomicity of the embedded connect step, and the auth prerequisite. Minor gap: it never says what happens if the purchase itself fails or whether the domain is immediately active.

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 years, domain, and the whole connect sub-object are already documented in the schema. The description adds only the framing that connect can be combined with the purchase call; the hostname/enum semantics come entirely from the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Purchase a domain') plus the payment mechanism and return signal, so the agent immediately knows the operation. It also references connect_domain as its equivalence point, though it does not distinguish itself from sibling buy_link or explain why to pick this over check_domain.

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?

It states the condition for using the optional `connect` path (point at a deployment 'in the same call', same as connect_domain), which is real when-to-use guidance. It stops short of explicitly telling the agent when to prefer calling connect_domain separately instead of folding it in.

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

All namemyapp 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