Skip to main content
Glama

buy_expired_domain

Browse and purchase expired closeout domains at discounted prices. Use 'list' to view available domains or 'buy' to acquire one.

Instructions

Browse and purchase expired closeout domains at discounted prices. Use action 'list' to see available domains or 'buy' to purchase one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction: 'list' available expired domains or 'buy' one
domainNoDomain name to buy (required for 'buy')
currencyNoCurrency for the purchase
paramsNoAdditional filter parameters for 'list'
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions two actions but lacks details on authentication, idempotency, side effects, or response format.

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 purpose, zero wasted words.

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

Completeness2/5

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

Missing output schema and description does not explain return values for list or buy, nor error conditions, leaving gaps for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by explaining the enum actions and their parameter requirements, though currency and params could be expanded.

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 browses and purchases expired closeout domains, distinguishing it from siblings like 'buy_it_now' and 'register_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 explicitly instructs to use 'list' to browse and 'buy' to purchase, but does not compare with alternative tools or specify when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/dynadot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server