Skip to main content
Glama

Set SSH hmac-sha1 support

vps_set_sha1_hmac
Idempotent

Allow or block the legacy hmac-sha1 MAC algorithms in sshd_config, then reload sshd; open sessions stay connected. Keep them blocked unless an old SSH client cannot connect without them. Check the current state with vps_get_ssh_security.

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

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, but the description adds context the annotations cannot: the change is applied to sshd_config and followed by an sshd reload, and existing open sessions are not dropped. That session-continuity note is exactly the kind of risk detail an agent needs before toggling a security setting. It stops short of saying whether a reload can fail or what confirmation is returned.

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 clauses, each doing distinct work: what changes and its side effect, the safe default, and the state-check alternative. The most important constraint (keep blocked by default) is front-loaded after the action statement with zero filler.

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 two-parameter toggle with full schema coverage and a safety annotation set, the description covers action, side effect, risk default and the read alternative. The only gap is that with no output schema, it does not indicate what a successful call returns or confirms.

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 'id' and 'enabled' are already documented in the schema, and the description adds no syntax or format detail beyond mapping 'allow or block' onto the boolean. Baseline 3 is appropriate when the schema carries the parameter burden.

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 pair ('Allow or block') plus the exact resource ('legacy hmac-sha1 MAC algorithms in sshd_config') and the side effect ('reload sshd'). An agent can distinguish this from the sibling cipher/KEX hardening tools without opening the 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 an explicit default posture ('Keep them blocked unless an old SSH client cannot connect without them'), which is a when-not-to-use rule, and names the read-path alternative ('Check the current state with vps_get_ssh_security'). Both the decision condition and the complementary tool are spelled out.

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.