skypilot-mcp

skypilot_tail_autostop_logs

Read-only

Retrieve autostop hook logs for a SkyPilot cluster to diagnose autostop events. View the last N lines (default 100) or all output.

Instructions

Get autostop hook logs (autostop_hook.log) for a cluster. Shows the log output from the autostop hook. Returns the last N lines (default 100, set to 0 for all).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_name": "<cluster_name>"
    },
    "name": "skypilot_tail_autostop_logs"
  }
}

Input Schema

Name	Required	Description	Default
`tail`	No
`cluster_name`	Yes

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 tells the agent this is a safe read. The description adds genuinely useful behavior beyond that: the log file name and the tail-count semantics (default 100, 0 means all). It does not cover error cases or what happens for a nonexistent/stopped cluster.

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 purpose and then the tail behavior. No filler or repetition of the tool name.

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-value explanation is not needed. The description covers purpose and the key parameter, but omits sibling differentiation and usage context for a tool that sits among several log-retrieval siblings.

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%, so the description has to carry the load. It does explain the non-obvious `tail` parameter (default 100, 0 = all lines), but `cluster_name` is left entirely to the schema/name inference. Partial compensation for the coverage gap.

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: retrieves the autostop hook log (autostop_hook.log) for a named cluster. The resource is concrete enough to separate it from the sibling skypilot_tail_provision_logs and skypilot_cluster_autostop, though it never names those alternatives explicitly.

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 says what it fetches but never says when to reach for it over siblings like skypilot_tail_provision_logs, skypilot_cluster_autostop, or skypilot_api_server_logs. No prerequisites or exclusion conditions are given.

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

Deploy Server