Skip to main content
Glama

Delete webspace SSH key

webspace_delete_ssh_key
Destructive

Remove an SSH key from a webspace's authorized_keys by its fingerprint id. Destructive: requires confirm=true.

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>",
      "fingerprint": "<fingerprint>",
      "confirm": "<confirm>"
    },
    "name": "webspace_delete_ssh_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
confirmYesMust be true to confirm this destructive operation
fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value by naming the exact mutation target (authorized_keys) and the confirm=true requirement, but says nothing about what happens when the key is not found or whether removal is immediate or reversible.

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 tight sentences, front-loaded with the operation and object, with the destructive caveat placed prominently at the end. No 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 three-parameter delete with annotations carrying the safety profile and no output schema, the description covers operation, target, and the confirm gate. A pointer to the list-ssh-keys tool as the source of the fingerprint 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?

Schema coverage is 67%; 'id' and 'confirm' are documented in the schema, while 'fingerprint' is bare. The description compensates by framing `fingerprint` as 'its fingerprint id', which is the only added semantic, so the baseline of 3 fits.

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?

States a specific verb and resource: it removes an SSH key from a webspace's authorized_keys, keyed by fingerprint id. The webspace scope is clear in the text, so it is distinguishable from vps_delete_ssh_key, though the description never explicitly contrasts them.

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 by the name and the 'remove an SSH key' phrasing, but there is no explicit when-to-use guidance, no prerequisite about first listing keys to obtain the fingerprint, and no statement of what to do if the key is absent.

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.