Skip to main content
Glama

Rotate a rental's IP address

rotate_ip
Destructive

CHANGES STATE, costs nothing. Ask for a new IP address on one of the account's rentals. Connections open through the device may drop while it changes. Rotating too soon is refused with the number of seconds to wait; the dashboard's limits apply. Needs a read-write API key, an agent token that may buy, or the order's invoice ID.

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": {
      "rentalId": "<rentalId>"
    },
    "name": "rotate_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
rentalIdYesRental id from list_rentals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds materially beyond them: connections may drop mid-change, the operation costs nothing, premature calls are rejected with a seconds-to-wait value, and it lists the three accepted credential forms (read-write key, purchasing agent token, or invoice ID). That is exactly the sidelined context an agent needs before a destructive call.

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?

Four short sentences, with the state-changing warning and zero cost front-loaded, followed by side effects, rate limits, and auth. Every sentence carries distinct information and nothing is repeated from the title.

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 one-parameter destructive tool with no output schema, the description covers safety, side effects, cost, rate limits, and authentication. Nothing an agent needs in order to call it correctly is missing.

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?

There is a single parameter and schema coverage is 100%, with the schema itself saying 'Rental id from list_rentals.' The description reinforces the scope ('one of the account's rentals') but adds no format or sourcing detail beyond the schema, so the baseline of 3 applies.

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 second sentence names a specific verb and resource: 'Ask for a new IP address on one of the account's rentals.' Combined with the lead 'CHANGES STATE', an agent can distinguish this from extend_rental or buy_traffic_pack without opening any schema.

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 precondition (an existing rental on the account) and the rate-limit condition under which rotation is refused, which is strong context for deciding whether to call. It stops short of naming an explicit alternative or a 'do not use when' case, so it does not reach the top band.

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