Skip to main content
Glama
Sign In

asms

by ai.asms
OverviewDiscussionsAdmin

Renew a rented number

renew_rental
Destructive

Keep a rented number for another period: the period is added to its current end, at today's price for that period in its country (see get_rental_offers). Possible from 2 hours after renting until 20 minutes before the end. Debits the wallet only if the renewal goes through. WARNING: this spends real wallet balance; confirm the number, period and price with the user first.

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": {
      "number": "<number>",
      "period": "<period>"
    },
    "name": "renew_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesThe rented number, as rent_number or list_rentals gave it ("+", spaces and dashes are ignored).
periodYesRental period: "oneDay" (1 day), "oneWeek" (1 week), "oneMonth" (1 month), "threeMonths" (3 months), "sixMonths" (6 months), "twelveMonths" (12 months). Not every period is on sale in every country: check get_rental_offers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructive and non-idempotent annotations, the description explains that the new period is appended to the current end, that pricing uses today's country price, that the wallet is debited only on success, and that the user should confirm number, period, and price first. These are material behavioral and financial details not available from annotations alone.

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: purpose first, then timing, billing, and a final safety warning. Every sentence contributes operational information without repetition.

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 financially destructive mutation with no output schema, the description covers timing, pricing, wallet debit, and confirmation requirements well. It does not describe the return value or specific failure cases such as insufficient balance or expired rental, leaving a minor completeness gap.

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%, so the baseline is 3. The description adds semantic meaning by clarifying that the period extends the current rental rather than replacing it and that price depends on the period and country, though it adds little about the number parameter beyond the schema's own formatting notes.

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 gives a specific verb and resource: keeping a rented number for another period. It clearly distinguishes renewal from renting a new number or cancelling a rental, so an agent can identify the operation immediately.

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 eligible window precisely: from 2 hours after renting until 20 minutes before the end, and points to get_rental_offers for prices and availability. It does not explicitly compare against rent_number or set_rental_auto_renew, but the renewal context is clear.

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

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