Skip to main content
Glama

Vee3

by io.github.Vee3io

domains.register

Register a domain through Vee3.

The user or agent passes registrant contact details and expected_token_cost from domains.registration_quote. Use a real registrant email address the domain owner can access; the registrar may send a verification email that must be completed to keep the domain in good standing. Charges the quoted token cost on success.

Cost = 200 tokens + domain registration price in tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRegistration term in years.
domainYesDomain name to register (for example example.com).
contactYesRegistrant contact used for Registrant, Admin, Tech, and AuxBilling roles. Object with first_name, last_name, address1, city, state_province, postal_code, country (two-letter code), phone (format +NNN.NNNNNNNNNN), and email_address (a real inbox the registrant can access; the registrar may send a verification email that must be completed). Optional fields: address2 and organization_name.
enable_privacyNoWhether to enable free WhoisGuard privacy protection when available.
expected_token_costYesToken cost from a fresh domains.registration_quote response. Required to prevent surprise charges.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRegistration term in years.
domainNoRegistered domain name.
order_idNoNamecheap order identifier for the registration purchase.
expires_atNoDomain expiration timestamp when known.
registeredNoWhether registration completed successfully.
token_costNoTokens charged for this registration (200 service tokens plus the domain price in tokens).
privacy_enabledNoWhether WhoisGuard privacy protection is enabled.
namecheap_domain_idNoNamecheap domain identifier for the managed domain.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contact / description
      Previous value: -"Registrant contact used for Registrant, Admin, Tech, and AuxBilling roles. Object with first_name, last_name, address1, city, state_province, postal_code, country (two-letter code), phone (format +NNN.NNNNNNNNNN), and email_address. Optional fields: address2 and organization_name."New value: +"Registrant contact used for Registrant, Admin, Tech, and AuxBilling roles. Object with first_name, last_name, address1, city, state_province, postal_code, country (two-letter code), phone (format +NNN.NNNNNNNNNN), and email_address (a real inbox the registrant can access; the registrar may send a verification email that must be completed). Optional fields: address2 and organization_name."
    • changedOutput schema / properties / token_cost / description
      Previous value: -"Tokens charged for this registration."New value: +"Tokens charged for this registration (200 service tokens plus the domain price in tokens)."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses the token cost formula and the fact that a verification email may be sent that must be completed. Since no annotations are provided, this carries the full burden and covers key behavioral outcomes. It does not mention reversibility or other side effects, but the most important behaviors are disclosed.

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 compact and front-loaded. The first sentence states the purpose, the second gives actionable workflow, and the final formula is unambiguous. Every sentence earns its place with no fluff.

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?

The description covers the prerequisite (registration_quote), the expected inputs, the cost, and the verification requirement. With a full output schema present, this is sufficient for correct use. It does not need to describe return values.

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?

The description clarifies that expected_token_cost comes from a fresh domains.registration_quote response, adding meaning beyond the schema's generic description. It also ties the contact details to registrant roles, augmenting the schema. With 100% schema coverage, this adds valuable context beyond the baseline.

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 'Register a domain through Vee3' with a specific verb and resource. It distinguishes itself from sibling tools like domains.renew and domains.registration_quote by indicating it performs the actual registration, not a quote or renewal.

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 explicitly instructs the user to pass registrant contact details and expected_token_cost from domains.registration_quote, establishing a clear prerequisite workflow. It also advises using a real email address and notes the verification requirement, giving contextual usage guidance. However, it does not explicitly state when not to use the tool (e.g., for renewals).

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources