Skip to main content
Glama

List power schedules

list_power_schedules
Read-only

List a cluster's power schedules: the scheduled one-off or repeated stop/start actions attached to an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus). Each entry shows its id, action (stop or start), schedule_kind ('once' fires at run_at; 'cron' fires per cron_expression in timezone), enabled flag, next_run_at, and the outcome of its last run (completed, skipped, deferred, or failed, with detail). Use it before create_power_schedule (to avoid duplicates - at most 20 schedules per cluster) and to get the schedule_id for update_power_schedule / delete_power_schedule. Read-only. Not available for managed-Kubernetes or plain imported clusters.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses the per-entry return fields (id, action, schedule_kind, enabled, next_run_at, last-run outcome including skipped/deferred/failed with detail) and the 'once' vs 'cron' timing semantics. It also surfaces two operational constraints an agent needs — the 20-schedule cap and the cluster-type availability restriction.

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?

Front-loaded with the core action and resource, then limits, then usage routing — the ordering is sensible. It runs as one dense paragraph and the long provider enumeration is slightly heavy, though it does earn its place by defining the availability scope.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields and outcome values. Combined with the cap, availability caveats, and downstream tool routing, an agent has everything needed to call this correctly and interpret results.

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 coverage is 100%, with both cluster_id and cluster_name documented including the 'optional when a cluster is selected' fallback, so the schema carries the parameter burden. The description adds no identifier-selection guidance or format hints beyond that, which is the expected baseline when the schema is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a cluster's power schedules') and immediately defines the resource as scheduled one-off or repeated stop/start actions on an Ankra-provisioned self-managed cluster. It further narrows scope by naming the supported providers and excluding managed-Kubernetes/imported clusters, so an agent can distinguish it from generic cluster tools without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: call it before create_power_schedule to avoid duplicates (citing the 20-per-cluster cap) and to obtain the schedule_id needed by update_power_schedule / delete_power_schedule. It also states when the tool is unavailable (managed-Kubernetes or plain imported clusters), which is the kind of exclusion most definitions omit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.