Skip to main content
Glama

Vee3

by io.github.Vee3io

domains.renew

Renew a domain already managed through this Vee3 account.

The user or agent passes expected_token_cost from domains.renewal_quote. Charges the quoted token cost on success. Premium domains can only be renewed for 1 year at a time.

Cost = 100 tokens + domain renewal price in tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRenewal term in years. Premium domains support 1 year only.
domainYesManaged domain name to renew (for example example.com).
expected_token_costYesToken cost from a fresh domains.renewal_quote response. Required to prevent surprise charges.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRenewal term in years.
domainNoRenewed domain name.
renewedNoWhether renewal completed successfully.
order_idNoNamecheap order identifier for the renewal purchase.
expires_atNoUpdated domain expiration timestamp when known.
token_costNoTokens charged for this renewal (100 service tokens plus the domain renewal price in tokens).
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. Changed1 schema field changed
    • changedOutput schema / properties / token_cost / description
      Previous value: -"Tokens charged for this renewal."New value: +"Tokens charged for this renewal (100 service tokens plus the domain renewal price in tokens)."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility. It discloses the exact cost formula (100 tokens + renewal price), that charges occur only on success, and the premium renewal constraint. This is critical behavioral context beyond the input schema and informs the agent of financial consequences.

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 highly concise: three sentences and a cost formula line. Every sentence adds necessary information—purpose, prerequisite workflow, premium limitation, and cost. It is front-loaded with the core action and contains no fluff or redundancy.

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 transactional tool with cost and constraints, the description thoroughly covers the workflow, cost structure, and premium domain behavior. The output schema exists to document return values, and the input schema already documents all parameters, so no critical operational detail is missing.

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%, giving a baseline of 3. The description adds value by explaining that expected_token_cost comes from a fresh domains.renewal_quote response and is used to prevent surprise charges, and reinforces the years constraint for premium domains. This deepens understanding beyond the schema's own descriptions.

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 'Renew a domain already managed through this Vee3 account', which specifies the exact action and resource scope. It distinguishes itself from sibling tools like domains.register (for new domains) and domains.renewal_quote (for quoting) by emphasizing 'already managed'.

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 gives explicit guidance to pass expected_token_cost from domains.renewal_quote, establishing a clear prerequisite workflow. It also notes the premium domain 1-year limitation. However, it does not explicitly state when not to use the tool (e.g., unmanaged domains), though that is implied by 'already managed'.

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