Skip to main content
Glama

Get node cloud init log

get_node_cloud_init_log
Read-only

Read the cloud-init status and the tail of /var/log/cloud-init-output.log for one node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud), over SSH-via-bastion. This is the debug surface for node-group user_data: that document runs once, at first boot, before anything else can observe it, so a failed provisioning script is invisible to every other tool - the node either joins looking perfectly healthy (cloud-init's growpart fallback restores an ordinary full-disk root when a carve fails) or never appears at all. Use it when a node group carries user_data and a node came up wrong: partitions or mounts that are missing, a package that should have been installed, a first-boot script whose effect is absent. Returns cloud-init's own status (including whether it reported an error) plus the output-log tail, and runs nothing that changes the node. Repeated calls attach to an in-flight fetch instead of dispatching a duplicate. Identify the node with node_id (preferred, from list_cluster_nodes) or node_name. Not available for imported or managed-Kubernetes clusters. For OS-level failures unrelated to first boot, use ssh_diagnose_node.

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

Input Schema

NameRequiredDescriptionDefault
node_idNoUUID of the node to diagnose. Preferred when known (from list_cluster_nodes).
node_nameNoExact name of the node to diagnose. Alternative to node_id.
cluster_idNoUUID of the cluster the node belongs to. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster the node belongs to. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses the connection path (SSH-via-bastion), the return payload (cloud-init status including error flag plus log tail), the safety guarantee ('runs nothing that changes the node'), and an idempotency trait ('Repeated calls attach to an in-flight fetch instead of dispatching a duplicate'). It also explains why the gap exists, since user_data is invisible to every other tool.

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 verb and resource, then the failure mode, the return value, and the exclusions in a sensible order. It runs long as a single dense block, and the growpart parenthetical is informative but heavy for a tool description.

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 still explains what comes back (status plus output-log tail). Combined with the prerequisites, exclusions, node identification guidance, and idempotency behavior, there is nothing material an agent needs before calling it.

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?

Schema coverage is already 100%, so the baseline is 3. The description adds slight routing value by restating node_id as preferred with a source (list_cluster_nodes) and node_name as the alternative, but it says nothing extra about cluster_id/cluster_name resolution, so the gain over the schema text is marginal.

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: read cloud-init status plus the tail of /var/log/cloud-init-output.log for one node, over SSH-via-bastion, on named providers. This is clearly distinguishable from sibling log tools like get_pod_logs or ssh_diagnose_node.

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 a concrete triggering condition ('use it when a node group carries user_data and a node came up wrong: partitions or mounts that are missing, a package that should have been installed'), an explicit exclusion ('Not available for imported or managed-Kubernetes clusters'), and an alternative for the adjacent case ('For OS-level failures unrelated to first boot, use ssh_diagnose_node').

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.