Skip to main content
Glama
ample-run

@amplerun/mcp

Official
by ample-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search GPU offers

search_offers
Read-onlyIdempotent

Find GPU machines available for rent by model, count, VRAM, region, and hourly price. Returns cheapest offers first with pagination and optional template fit checks.

Instructions

Search GPU machines that can be rented now on AmpleRun. gpu_model, gpu_count and max_rate_micro_per_hour filter on the server. min_vram_gib and region filter each fetched page here because the API has no such filters, so a page can return fewer than limit matches: scanned is how many offers were checked, and next_cursor continues. Prices are micro-units per hour for the whole machine, fee included; cheapest first. With template, each offer carries fit {fits, reason}. Read-only; no API key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1 to 100.
cursorNonext_cursor from the previous page.
regionNoCase-insensitive part of the host's cloud region, e.g. "us-east". Offers without a reported region are excluded.
templateNoTemplate slug such as "pytorch-cuda", or its id (UUID), from list_templates.
gpu_countNoMinimum number of GPUs in the machine.
gpu_modelNoCase-insensitive part of the GPU model name, e.g. "4090" or "A100".
min_vram_gibNoMinimum VRAM per GPU in GiB. Offers with unmeasured VRAM are excluded.
max_rate_micro_per_hourNoHighest machine price per hour in micro-units, e.g. "500000" for 0.50 USDC/h.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/openWorld, but the description adds non-obvious behavior: no API key needed, client-side filtering that can yield fewer than `limit` matches, the meaning of `scanned`, cursor continuation, and price units. This is exactly the extra context that helps an agent interpret results.

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?

Front-loaded with purpose and filtering model, then pagination, pricing, template fit, and safety in two tight sentences. Every clause carries information; 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?

No output schema exists, and the description compensates by explaining the return shape: cheapest-first ordering, price units, `scanned`, `next_cursor`, and the per-offer `fit` object with template. An agent has everything needed to page and interpret results.

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?

Schema coverage is 100%, so per-parameter docs already exist (baseline 3). The description goes further by explaining the semantic split between server-side and per-page filters and by clarifying that prices are whole-machine micro-units including fees, which the schema does not state.

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 ('Search GPU machines that can be rented now on AmpleRun'), which clearly distinguishes it from siblings like list_templates and create_rental. The purpose is immediately graspable without opening the 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?

Gives strong operational context: which filters run server-side vs per-page, how to continue with next_cursor, and that template adds fit info. It stops short of explicitly naming alternatives or when-not conditions (e.g., 'use create_rental after selecting an offer'), so it isn't a full 5.

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