Skip to main content
Glama

List your active rentals

list_rentals
Read-onlyIdempotent

Read-only, free. List the account's active proxy rentals with their connection details (host, ports, username, password), end time, online state, current IP and whether each can rotate or extend. The connection details are secrets: keep them in the user's own configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rentals"
  }
}

Input 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 description adds real context beyond the annotations: the 'free' cost characteristic, the presence of secrets in the response, and an explicit handling instruction to keep credentials in the user's own configuration. The read-only/idempotent/no-destructive traits are already covered by annotations and are merely restated.

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 short sentences, front-loaded with safety and cost, then the return shape, then the credential-handling caveat. Every sentence carries distinct information with no filler.

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?

With no output schema and zero parameters, the description does the necessary work by enumerating the returned fields and flagging the secret-handling requirement. It stops short of covering result volume, pagination, or the behavior when no active rentals exist.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly avoids inventing filtering options that the schema does not support.

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?

States a specific verb and resource ('List the account's active proxy rentals') and enumerates exactly what each record contains (connection details, end time, online state, current IP, rotate/extend flags). It does not explicitly name a sibling such as get_rental for a single rental, so differentiation is left implicit through the word 'active' and the plural scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read-only, free' signals this is a safe, zero-cost call, which implies usage. However, there is no explicit statement of when to call this versus get_rental (single rental) or get_traffic_connection, and no exclusions or preconditions are given.

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