skypilot-mcp

skypilot_list_accelerator_counts

Read-only

List available accelerators and their counts across clouds, with filters for name, region, quantity, and cloud to check capacity before provisioning.

Instructions

List available accelerators and their available counts. Returns a mapping of accelerator names to available quantities. Filter by name, region, quantity, or specific clouds.

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

Input Schema

Name	Required	Description	Default
`clouds`	No
`gpus_only`	No
`name_filter`	No
`region_filter`	No
`quantity_filter`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds that it 'Returns a mapping of accelerator names to available quantities', but since an output schema exists this return-shape note is largely redundant, and it says nothing about filtering defaults or scope behavior.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action followed by return and filter detail. No filler, though the return sentence partly duplicates output-schema information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output-schema presence relieves it of explaining return values, but for a 5-parameter tool with 0% schema description coverage, the description leaves gpus_only and all defaults unaddressed, and provides no help distinguishing it from skypilot_list_accelerators.

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 description coverage is 0% across 5 parameters, so the description must carry more. It names four filter dimensions (name, region, quantity, clouds) that map to name_filter, region_filter, quantity_filter, and clouds, but leaves gpus_only undocumented and adds no format, syntax, or default semantics.

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 available accelerators and their available counts') and clarifies scope by noting it returns a mapping of names to quantities. It is clear about what it does, but does not explicitly distinguish itself from the nearby sibling skypilot_list_accelerators.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, prerequisites, or contrast with the very similar skypilot_list_accelerators sibling. The only usage hint is the list of filter dimensions, which is implied rather than framed as a selection rule.

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

Deploy Server