skypilot-mcp

skypilot_dashboard

Read-only

Open the SkyPilot dashboard in the default web browser to view and manage clusters, jobs, and storage, with an optional starting page.

Instructions

Open the SkyPilot dashboard in the default web browser. Optionally specify a starting page.

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

Input Schema

Name	Required	Description	Default
`starting_page`	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?

Annotations only declare readOnlyHint=true, so the description must carry most of the behavioral burden. It usefully discloses the observable side effect that a browser window is launched and that a page can be preset, but says nothing about prerequisites (server running, authentication) or whether the call blocks awaiting the UI. Partial but real added context.

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?

Two short sentences with the primary action front-loaded and the optional parameter mentioned second. No waste, though it is minimal rather than maximally informative.

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?

An output schema exists, so return values need not be explained, and the safety profile is covered by readOnlyHint. However, the description omits any prerequisite or authentication context for a tool that depends on a live SkyPilot environment, leaving a gap for an otherwise simple definition.

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% for the single optional starting_page parameter, so the description must compensate. It does state the parameter is optional and controls the landing page, which is meaningful, but gives no accepted values or format examples (e.g., 'jobs', 'clusters'), leaving ambiguity.

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 states a specific verb ('Open'), resource ('SkyPilot dashboard'), and medium ('default web browser'), so an agent immediately understands the action. It does not explicitly distinguish itself from the sibling skypilot_jobs_dashboard, which is a plausible source of confusion, so it falls short of a 5.

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 statement of when to use this tool versus alternatives, no mention of the closely related skypilot_jobs_dashboard sibling, and no prerequisites such as a running API server or prior login. Usage is only implied by the verb.

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

Deploy Server