skypilot-mcp

skypilot_storage_ls

Read-only

List all SkyPilot-managed storage objects, including cloud buckets, to inspect available storage resources for cluster and job workflows.

Instructions

List all SkyPilot-managed storage objects (cloud buckets).

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_storage_ls"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.5/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 operation, and the description adds the useful scoping detail that the objects are cloud buckets. It does not describe ordering, pagination, or whether empty results are possible, but with annotations covering safety and an output schema present, a 3 is appropriate.

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?

A single front-loaded sentence with no filler; every word (SkyPilot-managed, storage objects, cloud buckets) narrows scope. Nothing is wasted.

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?

Given zero parameters, a 100%-covered (empty) schema, and a dedicated output schema, the description needn't explain return values. It is essentially complete for a simple list tool, only lacking sibling disambiguation.

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?

The tool takes zero parameters, which is the baseline for a 4. There is nothing further the description could add about inputs, and no arguments exist that need documenting.

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 (List) and resource (SkyPilot-managed storage objects), then clarifies with 'cloud buckets' so the agent knows exactly what is returned. It clearly differs from skypilot_storage_delete, though it doesn't verbally distinguish itself from the similarly-named skypilot_volume_ls sibling.

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?

There is no explicit when-to-use guidance, prerequisites, or named alternative. The listing intent is implied by 'List all,' but the agent must infer when this is preferable to skypilot_volume_ls or other status tools.

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

Deploy Server