Skip to main content
Glama

Set auto-renew / fund renewal vault

set_auto_renew
Destructive

Turn auto-renew on/off for a domain you own and/or fund its renewal balance (vault). deposit_usd moves USDC from your prepaid balance (topup_balance) into the domain's vault; withdraw_usd moves it back. The daily job renews 1 year when ≤30 days from expiry if the vault covers the price, otherwise emails reminders at 30/14/7/1 days.

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": "set_auto_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
api_keyNoOptional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.
enabledNo
deposit_usdNo
withdraw_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Optional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.",
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • removedInput schema / properties / auto_renew
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedInput schema / properties / deposit_usd
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / enabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withdraw_usd
      Added value: +{
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "auto_renew"
      -]New value: +[
      +  "domain"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the destructiveHint/openWorldHint annotations, the description discloses the automation contract: a daily job renews 1 year when ≤30 days from expiry, only if the vault covers the price, otherwise reminder emails go out at 30/14/7/1 days. What it does not disclose is the destruction vector implied by destructiveHint=true — e.g., that disabling auto-renew or an under-funded vault puts the domain at risk of expiring and being lost.

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?

Three sentences, front-loaded with the primary action, then fund-direction semantics, then the automated job's timing. No filler, and the parenthetical '(vault)' disambiguates the term once instead of re-explaining it.

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 5-parameter destructive write tool with no output schema, the description covers purpose, fund flow, and the downstream automation that makes the tool consequential. It stops short of failure modes (insufficient prepaid balance, withdraw limits) and return/confirmation behavior, which an agent calling a money-moving tool would want.

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?

With only 20% schema coverage, the description must carry the parameter burden, and it does so well for deposit_usd and withdraw_usd by defining exactly which balance moves in which direction. It is weaker on `enabled` (never states it is the toggle or what omitting it does) and on amount constraints such as insufficient balance or withdrawing while a renewal is pending.

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 states two precise functions — toggling auto-renew for a domain and funding its renewal vault — and names the sibling resource (topup_balance) that supplies the money, so an agent can tell this apart from buying, renewing, or topping up. The verb+resource pairing is unambiguous.

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 clearly explains that deposit_usd pulls from prepaid balance into the vault while withdraw_usd reverses that flow, which tells the agent when to use each parameter. The gap is that it never contrasts this with the manual sibling renew_domain (pay-now vs let-the-daily-job-handle-it), so the choice between auto-renew funding and immediate renewal is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources