Skip to main content
Glama

Update OpenSSH

vps_update_openssh

Run the OS package manager to install the latest OpenSSH on the VM (apt/dnf/zypper).

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

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety bar is lower. The description adds real context by disclosing the mechanism (OS package manager, apt/dnf/zypper), but omits operational traits that matter for an SSH package upgrade: whether sshd is restarted, whether the session could drop, whether existing config is preserved, and how failures surface. No contradiction with 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?

One sentence, front-loaded with the action, with the package-manager hint appended rather than buried. No redundant restatement of the title.

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 one-parameter mutation tool with no output schema, the description should say what the agent gets back (new version, exit status) or at least that the operation can take time or disrupt SSH. Neither is covered, leaving a meaningful gap for a tool that modifies system packages.

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% and the single `id` parameter is fully documented as the VPS ID. The description adds nothing about the parameter, which is acceptable given the schema does the work, so the baseline 3 applies.

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 concrete action and resource: install the latest OpenSSH on the VM, and even names the mechanism (apt/dnf/zypper). That clearly separates it from the ssh-key CRUD siblings. It does not explicitly contrast with vps_exec, which could also install packages, so it falls just short of a 5.

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 only implied: an agent can infer 'call this when you want current OpenSSH on the box.' There is no statement of when to prefer it over vps_exec, whether it is safe to re-run, or any prerequisite (e.g., reachable package repos, root access).

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.