Skip to main content
Glama
Sign In
Termix MCP Server

Termix MCP Server

by kalmma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_ssh_hosts

Lists all saved SSH hosts for the authenticated Termix user, enabling quick access to your configured SSH connections.

Instructions

List all saved SSH hosts for the authenticated Termix user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
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 disclosing behavior. It states that it lists hosts, but does not mention whether the operation is read-only, what data is returned, or whether any filtering/pagination exists. For a safety-critical operation, more transparency would be needed.

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 is a single, well-structured sentence with no redundant words. It is front-loaded and communicates the essential information efficiently.

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 simple zero-parameter list tool with no output schema, the description is largely complete: it identifies the resource and user scope. However, it does not specify the return format or any potential limitations (e.g., pagination), so there is slight room for improvement.

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 has zero parameters, so the baseline of 4 applies. The description correctly implies that no arguments are required, aligning with the schema. No additional parameter information is needed.

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?

The description uses a specific verb 'List' with a clear resource 'saved SSH hosts' scoped to 'authenticated Termix user'. This distinguishes it from singular siblings like get_ssh_host, making its purpose immediately obvious.

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?

While the description clearly implies a listing operation, it does not explicitly mention when to use this over alternatives such as get_ssh_host for individual hosts. The absence of exclusionary guidance is a minor gap, but the use case is fairly obvious.

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

Deploy Server

Other Tools