Skip to main content
Glama
Sign In
@amplerun/mcp

@amplerun/mcp

Official
by ample-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List my rentals

list_rentals
Read-onlyIdempotent

Retrieve your account’s AmpleRun GPU rentals with state, charges, rate, and funded-through time; paginate by cursor. Read-only view for monitoring active rentals.

Instructions

List the account's AmpleRun rentals with state, charge so far (micro-units), rate and funded-through time. Ordered by id, not by time; page with next_cursor. Read-only. get_rental gives details and access for one rental.

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
limitNoPage size, 1 to 100.
cursorNonext_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely non-obvious behavior: ordering is by id, not time, and pagination is driven by next_cursor, which an agent could not infer from the annotations.

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 compact clauses front-load what is returned, then ordering, then the sibling pointer. Every sentence earns its place with no filler.

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?

With no output schema, the description takes responsibility for the return fields and pagination model, and it does so. An agent has everything needed to call and interpret this listing correctly.

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%, with both limit and cursor fully documented, so the baseline is 3. The description's 'page with next_cursor' merely restates the schema's cursor semantics rather than adding format or edge-case detail.

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?

States a specific verb and resource (list the account's rentals) and enumerates the fields returned (state, charge, rate, funded-through time). It explicitly differentiates from the sibling get_rental, so an agent can distinguish the two without opening a 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?

The closing sentence names the alternative (get_rental for one rental's details/access), which tells the agent when to prefer this listing tool. It stops short of explicitly stating 'use this to browse all rentals', so it is strong but not a full when/when-not statement.

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

Deploy Server

Other Tools