Skip to main content
Glama
Sign In

Voxisim

by com.voxisim
OverviewDiscussionsAdmin

Extend a rental

sms_rental_extend
Destructive

Rented SMS numbers. Extend a rented number by N more hours. Deducts USD from the account balance. Use sms_rental_list_extend_options first for the available durations and their prices.

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": {
      "rental_id": "<rental_id>",
      "hours": "<hours>"
    },
    "name": "sms_rental_extend"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYes
rental_idYesRental id (UUID)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, destructive operation. The description adds important behavioral context beyond annotations by stating that USD is deducted from the account balance and that durations/prices should be checked first. It stops short of covering insufficient-balance handling or whether extension is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core operation and billing consequence. The fragment 'Rented SMS numbers.' is slightly wasteful, but the remaining sentences are efficient and actionable.

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?

An output schema exists, so return values need not be explained. The description covers the main billing effect and the required prerequisite lookup, which are the critical context for this destructive extension tool. It could be stronger by noting failure modes or whether extension starts from current expiry.

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

Parameters3/5

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

Schema coverage is only 50%, with rental_id documented as a UUID and hours left undocumented in the schema. The description clarifies that hours means additional hours ('N more hours'), but it adds no further meaning for rental_id or constraints on hours.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Extend a rented number by N more hours.' It distinguishes the operation from siblings through the prerequisite reference to sms_rental_list_extend_options, though the opening fragment 'Rented SMS numbers.' is less precise than the rest.

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 the agent to call sms_rental_list_extend_options first for available durations and prices. It does not discuss when to extend versus cancel or buy a new number, but the key prerequisite is clear.

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

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