Skip to main content
Glama

ssh_view_config

View SSH server configurations and settings to manage remote connections and monitor setup details.

Instructions

View the full SSH configuration including servers and settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for ssh_view_config which returns a sanitized view of the SSH configuration.
    case 'ssh_view_config': {
      // Filter out sensitive information (passwords and private key paths)
      const sanitizedConfig = {
        servers: config.servers.map(s => ({
          id: s.id,
          name: s.name,
          host: s.host,
          port: s.port,
          username: s.username,
          authMethod: s.authMethod,
          // Exclude: password, privateKeyPath for security
        })),
        settings: config.settings,
      };
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(sanitizedConfig, null, 2),
          },
        ],
      };
    }
  • src/index.ts:53-60 (registration)
    Registration of the ssh_view_config tool definition.
    {
      name: 'ssh_view_config',
      description: 'View the full SSH configuration including servers and settings',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'View' implies a read-only operation, the description fails to disclose return format, potential errors, whether credentials are exposed, or any side effects. The agent lacks information about what 'configuration' actually contains beyond the mention of servers and settings.

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?

The description consists of a single efficient sentence that is appropriately front-loaded with the action verb. There is no redundant or wasteful text, and the length is appropriate for a parameterless inspection tool.

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?

Given the absence of an output schema, the description minimally compensates by mentioning 'servers and settings' as content, but fails to indicate return format (JSON, text, structured object). For a simple read-only tool with no parameters, the description is adequate but has a clear gap regarding output expectations.

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 input schema has zero parameters, which per evaluation rules establishes a baseline score of 4. No parameter documentation is required or expected given the empty 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 provides a clear verb ('View') and resource ('SSH configuration') with scope indicators ('full', 'including servers and settings'). It implicitly distinguishes from sibling ssh_list_servers by emphasizing 'full configuration' rather than just a list, though it could explicitly mention this distinction for clarity.

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

Usage Guidelines2/5

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

The description states what the tool does but provides no guidance on when to use it versus alternatives. It does not indicate when to prefer this over ssh_list_servers or whether it should be called before other operations like ssh_connect.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hydroCoderClaud/mcpHydroSSH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server