Skip to main content
Glama
Sign In

rent.dev

by dev.rent
OverviewDiscussionsAdmin

List providers

rent_list_providers
Read-onlyIdempotent

Lists rent.dev's provider catalog as compact summaries: each provider's capabilities (offerings, pricing types, interfaces, auth and product capabilities), display-only summary_verdict, agentic flag, the provenance of its cheapest matched offering and that offering's price row. Read-only and anonymous on /mcp/public. A listed provider may be unpriced: its terms may permit display but not comparison (clause names that denial and its prices are withheld), no price row may match the filters, or its rows may carry no hourly figure (a GPU row then gives unpriced_reason: monthly_rate, no_time_unit or unknown_gpu_count; a per-unit row has usd and unit but no hourly figure). include_offerings carries every matching offering, not just the cheapest. use asserts a rights use on providers and figures (default display). limit caps providers only. Every offer carries covers, gpu.count, region_id and comparison_group: the group names the purchasable unit (GPU model, count, market, pricing type, canonical region and commitment), so two offers are price-comparable exactly when their groups match. region accepts the vendor's label or the canonical id; gpu_count, covers and figure narrow the grain.

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

Input Schema

NameRequiredDescriptionDefault
cpuNoThe CPU capacity class (`shared`, `dedicated`) or the vendor's product label for a CPU offering (e.g. `macos`), matched without regard to case.
gpuNoCanonical GPU model id (`h100-sxm-80gb`) or the vendor's own label.
useNoThe use the answer asserts: only providers permitting it are listed and only figures whose `publish_mask` allows it are shown. Default `display`.
limitNoMost providers to list, 1-200. Default 50.
coversNoKeep offerings whose figure covers this unit: `gpu` one GPU, `node`/`instance` a whole node or instance, `gpu_line_item` a fractional GPU line.
figureNoKeep offerings whose figure was produced this way (`listed`, `floor`, …).
regionNoA region label or a canonical region id (`us-east-1`), matched without regard to case; either spelling finds every offer in that place.
providerNoOne provider id, e.g. `runpod`.
gpu_countNoKeep GPU offerings whose `gpu.count` (GPUs per priced unit) is exactly this many; `gpu_count=1` asks for single-GPU offers only.
capabilityNoA capability the provider or one of its products lists, e.g. `gpu`, `serverless`, `sdk`, `mcp`, `api_key`.
agentic_onlyNoTrue keeps only providers with a product passing the three-test agentic conjunction.
architectureNoKeep CPU offerings whose architecture the vendor states as this value.
comparison_groupNoKeep offerings in exactly this comparison group; `cheapest_offering.comparison_group` names it, and the group's other offers are its comparable peers.
max_usd_per_hourNoKeep offerings whose hourly figure (`usd_per_gpu_hour` on a GPU row, else `usd_per_hour`) is at most this many USD.
include_offeringsNoTrue carries every matching offering of the listed providers, not just the cheapest.
max_usd_per_vcpu_hourNoKeep CPU offerings whose `usd_per_vcpu_hour` is at most this many USD.

Output Schema

NameRequiredDescriptionDefault
totalYesProviders matching the filters, before `limit`.
offeringsNoEvery matching offering of the listed providers, when `include_offerings` is true.
providersYes
truncatedYesTrue when a requested list was cut at its ceiling.
attributionYesObligations owed beside the listed providers' figures; show them with the prices.
generated_atYesUTC timestamp of the catalog fold.
catalog_versionYesSHA-256 of the committed catalog artifact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: anonymous access on /mcp/public, the fact that listed providers may be unpriced, the clause-based denial of comparison rights with prices withheld, and the unpriced_reason values. It also discloses that limit caps providers only while include_offerings carries all offerings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead clause is front-loaded and the content is dense with real information, but the body is a single sprawling block of long parenthetical sentences that is harder to scan than it needs to be. Much of the unpriced-offering detail could be tightened without losing meaning.

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?

For a 16-parameter, zero-required filtering tool with an output schema, the definition covers grain, rights, comparability and unpriced cases thoroughly. The only gap is routing guidance relative to sibling tools, which the output schema does not supply.

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 the baseline is 3, but the description still adds meaning beyond the schema: limit caps providers not offerings, use asserts a rights use over both providers and figures, and comparison_group defines price-comparability precisely. This is above-baseline clarification rather than repetition.

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?

The description opens with a specific verb and resource: it lists rent.dev's provider catalog as compact summaries, then enumerates exactly what each summary contains (capabilities, summary_verdict, agentic flag, cheapest matched offering plus provenance). It is clearly distinct from the pod/sandbox siblings, though it never names them.

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 conveyed through filter semantics and grain-narrowing (region, gpu_count, covers, figure, comparison_group) rather than explicit 'use this when' guidance or named alternatives such as rent_quote. An agent can infer it is the discovery step before quoting or provisioning, but the definition never says so.

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

All rent.dev toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources