Skip to main content
Glama
ssh-mcp-pro

ssh-mcp-pro

by oaslananka

Connector Status

connector_status
Read-onlyIdempotent

Check the remote SSH connector profile, authentication mode, and credential broker readiness without exposing secrets. Verify configuration before opening sessions or running remote operations.

Instructions

Use this when ChatGPT or Claude needs to understand the remote connector profile, authentication mode, and credential broker readiness without exposing secrets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connector_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
authModeYes
toolProfileYes
maxHttpSessionsYes
oauthConfiguredYes
privateKeysInChatYes
credentialProviderYes
publicUrlConfiguredYes
safeRemoteToolsOnlyYes
httpSessionIdleTtlMsYes
credentialEntryInChatYes
hostAllowlistConfiguredYes
rawSudoExecutionDefaultYes
allowedOriginsConfiguredYes
credentialBrokerConfiguredYes
rawCommandExecutionDefaultYes
destructiveExecutionDefaultYes
nonLoopbackHttpRequiresAuthAndOriginsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.12
    • changedOutput schema / properties / toolProfile / enum
      Previous value: -[
      -  "full",
      -  "remote-safe",
      -  "chatgpt",
      -  "claude",
      -  "remote-readonly",
      -  "remote-broker"
      -]New value: +[
      +  "full",
      +  "remote-safe",
      +  "chatgpt",
      +  "claude",
      +  "gemini",
      +  "remote-readonly",
      +  "remote-broker"
      +]
  2. First observedv1.1.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuinely useful trait beyond them: the call is safe to make for diagnostics because it reports credential broker readiness 'without exposing secrets'. It stops short of saying whether the status is fetched live from the remote or read from cached config.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no repetition or padding. The phrase 'ChatGPT or Claude' is redundant framing that could be dropped, but it costs little.

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?

With an output schema present and rich annotations, the description only needs to establish scope and safety, which it does. The one gap an agent might care about is whether calling it performs a live remote probe or returns locally held configuration.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline applies. Nothing in the description misleads about inputs.

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 the resource (the remote connector profile) and enumerates the specific facts it exposes: authentication mode and credential broker readiness. That is far more specific than the title alone, though it never explicitly contrasts with nearby tools such as service_status or get_metrics.

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?

It opens with a trigger condition ('Use this when ... needs to understand the remote connector profile, authentication mode, and credential broker readiness'), which gives a workable when-to-use signal. However, that condition essentially restates the tool's own output, and there is no when-not guidance or named alternative for overlapping status checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.