Skip to main content
Glama
ssh-mcp-guard
by HostCrust

List guarded hosts

list_hosts
Read-onlyIdempotent

Retrieves configured SSH hosts and their server IDs from the local guard hosts file without network access, so agents can identify available targets before requesting actions.

Instructions

Hosts in the ssh-mcp-guard hosts file, with their server ids. No network access.

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_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is fully covered. The description adds that data comes from a specific on-disk hosts file and that each entry carries a server id, though 'No network access' largely restates openWorldHint=false. It says nothing about behavior when the file is missing, empty, or malformed.

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?

Two short fragments, front-loaded with the resource and return content. Efficient overall, though 'No network access.' is a dangling statement whose relevance to the caller is left implicit.

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?

For a zero-parameter tool this is close to sufficient, but with no output schema the description is the only source of return-shape information and it only vaguely says entries come 'with their server ids' — no mention of the other host fields, ordering, or empty/error states.

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 the baseline is 4; there is nothing the description needs to explain beyond the schema's empty object.

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 the resource precisely — hosts in the ssh-mcp-guard hosts file — and what is attached to each entry ('with their server ids'). The listing verb is only implied by the name/title, but the scope is narrow enough that an agent can tell it apart from get_receipts, run_action, and submit_approved.

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?

No explicit when-to-use or when-not-to-use guidance, and no named alternatives. The phrase 'No network access' implicitly signals that this is a cheap, offline local read rather than an action against remote machines, which is weak but real routing signal.

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