Skip to main content
Glama

Get webspace SSH details

webspace_get_ssh_info
Read-only

Return SSH connection details for a webspace: host, port, username, and host key fingerprint (for known_hosts setup).

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": "webspace_get_ssh_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description does add value by naming the returned fields, which matters because there is no output schema, and by explaining the fingerprint's purpose. It says nothing, however, about error behavior when a webspace has no SSH access, which is the main behavioral unknown for this call.

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 and resource, then the concrete return fields and the fingerprint's use case. Nothing is padded or repeated from the title.

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 tool with annotations covering safety, the definition is nearly complete: it tells the agent what comes back despite the absence of an output schema. Only the failure case (no SSH access, unknown id) is left unstated, a minor gap.

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?

There is a single parameter whose schema description coverage is 100% ('The webspace ID', with a 24-hex-character pattern), so the schema fully documents it. The description adds no meaning beyond the schema, which is acceptable at this coverage level but earns no extra credit.

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 (Return) and resource (SSH connection details for a webspace) and enumerates exactly which fields come back: host, port, username, host key fingerprint. That field list cleanly separates it from siblings such as webspace_list_ssh_keys or webspace_add_ssh_key, which deal with keys rather than connection parameters.

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?

The parenthetical '(for known_hosts setup)' implies a use case but the description never states when to call this instead of alternatives such as webspace_list_ssh_keys or webspace_get. Usage is implied rather than guided, with no exclusions or prerequisites.

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.