Skip to main content
Glama

Set SSH legacy ciphers

vps_set_legacy_ciphers
Idempotent

Toggle whether legacy CBC/3DES ciphers are allowed in sshd_config. Pass enabled=true to allow legacy ciphers.

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": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "vps_set_legacy_ciphers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
enabledYesWhether to enable or disable the setting.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation and repeatability profile is covered. The description adds that the change targets the sshd_config file specifically, which is useful context. It does not say whether sshd is reloaded or restarted for the change to take effect, nor what security consequence enabling legacy ciphers has — the gaps that matter most for this operation.

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 no filler, and the operational statement is front-loaded ahead of the parameter hint. It could be slightly tighter by merging the two ideas, but nothing is wasted.

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?

For a two-parameter mutation with full schema coverage and annotations, the definition is minimally complete enough to invoke correctly. It leaves out the post-change behavior (sshd reload requirement) and the security trade-off of enabling CBC/3DES, which an agent needs to act responsibly.

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 100%, so both id and enabled are already documented in the schema, and the baseline is 3. The description adds one useful clarification — that enabled=true means legacy ciphers become allowed — reinforcing the schema's directional meaning. It adds nothing about the id format or validation, but the schema's pattern covers that.

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 and resource: toggling whether legacy CBC/3DES ciphers are allowed in sshd_config. That is concrete enough to separate it from siblings such as vps_set_password_auth, vps_set_post_quantum_kex or vps_set_sha1_hmac, which touch different sshd settings. It stops short of explicitly naming those alternatives.

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 only guidance is 'Pass enabled=true to allow legacy ciphers,' which explains the parameter rather than when to use the tool. There is no indication of when legacy ciphers are appropriate or when to prefer a related hardening tool, and no warning about weakening SSH security.

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.