Skip to main content
Glama

Resync cluster SSH keys

resync_cluster_ssh_keys
Destructive

Re-run the cluster's SSH key sync (the twin of ankra cluster ssh-keys resync): marks the cluster's SSH key resource for an update, after which a platform operation re-applies the current key set to the provider's copy where the provider keeps one and to authorized_keys on every node, standalone VM and the bastion, failing by name on any host it cannot reach. Use this to repair a key the provider lost or rotated, or to retry a key change that failed on a host. Requires clusters.write.

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

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.3/5.0
Behavior5/5

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

Beyond the annotations, the description explains that the call marks the resource for update and that a platform operation re-applies keys across the provider copy, nodes, standalone VMs, and bastion. It also discloses failure behavior by host name and the required permission. This is meaningful operational context for a destructive, non-read-only action.

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?

The description is front-loaded and information-dense, with no obvious filler. The long parenthetical sentence is somewhat run-on, but its details about where keys are applied and failure behavior are useful rather than redundant.

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?

For a moderate-complexity mutation with full schema coverage, annotations, and no output schema, the description covers purpose, authorization, targets, and failure behavior well. It does not clarify whether the call is asynchronous or how completion should be checked, which would help an agent call and follow up correctly.

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?

The schema already documents both optional selectors, `cluster_id` and `cluster_name`, at 100% description coverage. The tool description adds no parameter-specific syntax, selection rules, or precedence information beyond the schema. A baseline 3 is appropriate.

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?

The description states a specific verb and resource: re-run the cluster's SSH key sync, mark the SSH key resource for update, and have the platform re-apply the current key set. It also scopes the operation to the provider copy, every node, standalone VMs, and the bastion, which makes the operation distinguishable from node-specific SSH repair tools.

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

Usage Guidelines4/5

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

It gives clear when-to-use guidance: repair a lost or rotated provider key, or retry a key change that failed on a host. It also states the required `clusters.write` permission. It does not explicitly name when to prefer a sibling tool instead, which keeps it from a 5.

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.