Skip to main content
Glama

Show one rental

get_rental
Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault
rentalIdYesRental id from list_rentals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the bar is lower. The description adds two things annotations cannot: that the call is free of charge and that the returned connection details are secrets the agent should keep in the user's own configuration — genuinely useful operational guidance.

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 with the safety profile front-loaded ('Read-only, free.'), then the payload, then the secrets caveat. Nothing is redundant and the most decision-relevant fact comes first.

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?

There is no output schema, so enumerating the returned fields (host, ports, username, password, end time, online state, current IP, rotate/extend capability) carries the return-value burden well. Only the not-found/inactive-rental case is left unaddressed, a minor gap for a single-parameter read.

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 100% and the rentalId is described there, including its provenance ('Rental id from list_rentals'). The description adds only the constraint that the rental must be one of the account's active rentals, which is a slight semantic gain, so the baseline 3 is right.

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 uses a specific verb ('Show') with a clearly scoped resource ('one of the account's active rentals') and enumerates the returned fields, so the agent can immediately distinguish it from the sibling list_rentals, which covers many rentals.

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?

Usage is implied: fetch details for a single rental identified by id. There is no explicit statement of when to prefer this over list_rentals or the rotate/extend siblings, and no note on what happens for an unknown or inactive id, but the 'active rentals' framing gives reasonable context.

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