Skip to main content
Glama

Get SSH security settings

vps_get_ssh_security
Read-only

Read a VPS's SSH hardening over SSH: password login, the Debian/Ubuntu banner, post-quantum key exchange, legacy ciphers, hmac-sha1 MACs and the OpenSSH version. Read it before vps_set_password_auth, vps_set_ssh_banner, vps_set_post_quantum_kex, vps_set_legacy_ciphers, vps_set_sha1_hmac or vps_update_openssh. Fails while the VPS is not reachable over SSH.

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>"
    },
    "name": "vps_get_ssh_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

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 readOnlyHint=true, so the safety profile is covered; the description adds the non-obvious mechanics that the read happens over SSH and fails when the host is unreachable. It does not describe authentication requirements or rate limits, but for a read-only probe the disclosed failure mode is the material trait.

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?

Two sentences with zero waste: the first front-loads what is read, the second gives the ordering rule and the failure condition. Dense but scannable, with no restatement of the title or annotations.

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 one-parameter read-only tool with no output schema, the enumeration of inspected fields effectively tells the agent what comes back, and the failure condition covers the operational edge case. Only a note on required SSH credentials or expected output shape would make it fully complete.

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?

Only one parameter (id), and the schema documents it at 100% coverage with a pattern and description. The description adds no further meaning about the ID, 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 (read) and resource (a VPS's SSH hardening) and enumerates exactly what is inspected: password login, banner, post-quantum KEX, legacy ciphers, sha1 MACs, OpenSSH version. This clearly separates it from the webspace_get_ssh_info sibling and from the vps_set_* mutation siblings.

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?

Explicitly routes the agent: 'Read it before' names all six setter tools it should precede, giving a concrete ordering rule rather than vague context. It also states a precondition for failure ('Fails while the VPS is not reachable over SSH'), so the agent knows when not to bother calling.

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.