Skip to main content
Glama

Set SSH post-quantum key exchange

vps_set_post_quantum_kex
Idempotent

Turn post-quantum key exchange (sntrup761x25519-sha512) on or off in sshd_config. Needs OpenSSH 9.0 or newer: check with vps_get_ssh_security, upgrade with vps_update_openssh. The new config is tested with sshd -t before sshd reloads and rolled back if the test fails; open sessions stay connected.

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_post_quantum_kex"
  }
}

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

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, yet the description adds genuinely new behavior: the config is validated with sshd -t, automatically rolled back on failure, and existing sessions remain connected. That failure-mode and blast-radius information is exactly what an agent needs before mutating sshd_config and is not derivable from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and algorithm, then prerequisite, then safety behavior. No filler, no restatement of the title, and each sentence carries distinct information.

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?

For a two-parameter mutation with no output schema, the description covers the action, the exact setting, the version prerequisite, the recovery path on failure, and the rollback guarantee. Nothing an agent needs in order to invoke this safely is missing.

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 parameters documented, so the schema carries the semantics of id and the enabled boolean. The description's 'on or off' phrasing loosely maps to enabled but adds no format, constraint, or edge-case detail beyond the schema, so the baseline 3 applies.

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 (turn on/off), a specific resource (post-quantum key exchange in sshd_config) and even names the exact algorithm sntrup761x25519-sha512. This is clearly distinguishable from neighboring SSH-hardening siblings such as vps_set_legacy_ciphers or vps_set_sha1_hmac without opening their schemas.

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 an explicit precondition (OpenSSH 9.0 or newer) and routes the agent to concrete sibling tools for the prerequisite path: check with vps_get_ssh_security, upgrade with vps_update_openssh. The agent knows both when the call will fail and what to do instead, which is more than most definitions provide.

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.