Skip to main content
Glama

Set SSH banner

vps_set_ssh_banner
Idempotent

Toggle whether the Debian/Ubuntu pre-auth SSH banner is hidden (DebianBanner no). Pass enabled=true to hide.

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

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

A3.9/5.0
Behavior4/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 safety profile is covered. The description adds genuinely new behavior context: it is an OS-scoped (Debian/Ubuntu) config toggle and the underlying value becomes 'DebianBanner no' — the inverted semantics are the key non-obvious trait. It does not say whether the change takes effect immediately or needs a restart.

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 short sentences, zero filler, with the scope and the parameter mapping front-loaded. Every clause carries information the agent needs.

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 simple two-parameter, idempotent, non-destructive toggle with no output schema, the description covers purpose, OS scope, and the critical inverted flag mapping. The only gap is whether the setting is applied live or requires an SSH reload/restart to take effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description earns extra credit by resolving a real ambiguity: the schema only says 'Whether to enable or disable the setting,' while the description clarifies that enabled=true means the banner is HIDDEN. That inverted mapping is essential and not derivable from the schema. The `id` parameter is left entirely to the schema.

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 names a specific verb+resource (set/toggle the pre-auth SSH banner on Debian/Ubuntu) and even cites the underlying config directive (DebianBanner no). It is clear what is being changed, though it does not explicitly distinguish itself from siblings like vps_get_ssh_security or vps_set_legacy_ciphers.

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

Usage Guidelines3/5

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

Usage is implied (SSH hardening on Debian/Ubuntu hosts) and the parameter mapping is given, but there is no explicit statement of when to use this versus the read-only vps_get_ssh_security sibling, nor any exclusion or prerequisite (e.g., whether the SSH config must be reloaded).

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.