Skip to main content
Glama
TMYTiMidlY

portal-mcp-server

by TMYTiMidlY
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

portal_host

Manage the SSH host registry by listing, registering, or removing hosts with optional tags for group-based task execution.

Instructions

Manage the SSH host registry.

Modes

  • action="list": list all known hosts. Includes hosts.yaml / runtime- registered entries AND every Host alias discoverable in the OpenSSH client config (~/.ssh/config + system-wide fallback; or only $PORTAL_SSH_CONFIG when it is an absolute path; or none of them when it is "none" — the ssh -F none analogue), resolving real HostName/User/Port. Each entry has a source field: "hosts.yaml", "runtime", "ssh-config", or a "…+ssh-config" overlay (metadata from the declared origin, connection params from ssh config). Example: portal_host(action="list")

  • action="register": add a host to the registry. Pass host (ip/hostname), or just name if ~/.ssh/config has a matching Host alias (registers a use_ssh_config overlay). Optional: user (default root), port (default 22), key_path (else asyncssh falls back to ~/.ssh/id_* or ssh-agent), tags (comma-separated, used by portal_exec's group_tag). Example: portal_host(action="register", name="web01", host="10.0.0.1", user="ubuntu", tags="web,prod")

  • action="remove": remove a host from the registry. Required: name. Example: portal_host(action="remove", name="web01")

Hosts already defined in ~/.ssh/config are auto-resolved on first use; explicit registration is only needed for tag-based grouping. This MCP tool only accepts key-based hosts — password auth is intentionally not exposed here so credentials cannot leak into LLM tool-call traces. To use password auth, declare the host in hosts.yaml with auth: password and a password_command:. See README §Authentication.

action="list" may include a per-host warnings array (e.g. a plaintext password: field in hosts.yaml that is being ignored). When present, relay these warnings to the user — they flag misconfigurations the user must fix, and server-side logs are not visible to them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNo
nameNo
portNo
tagsNo
userNoroot
actionYes
key_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations, description carries full burden. It details behavior: how hosts are resolved from multiple sources, the 'source' field, warnings array, password auth exclusion, and instruction to relay warnings. No contradictions.

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?

Description is well-structured with sections for each action and a note on authentication. While slightly lengthy, every sentence contributes necessary information and is logically organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (three actions, multiple sources, warnings, auth constraints), the description covers all essential contexts: source field, warnings handling, password auth exclusion, and integration with ssh config. Output schema exists, so return values are not required in description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but the description thoroughly explains each parameter (host, name, port, tags, user, action, key_path) with defaults and meanings, adding significant value beyond the bare schema.

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?

Description clearly states 'Manage the SSH host registry' and enumerates three distinct actions (list, register, remove) with examples. It differentiates the tool from siblings like portal_exec and portal_shell by focusing solely on host registry management.

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

Usage Guidelines5/5

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

Explicit guidance on when to use each action and when registration is necessary (e.g., 'Hosts already defined in ~/.ssh/config are auto-resolved... explicit registration is only needed for tag-based grouping'). Also notes when not to use the tool (password auth not exposed) and directs to alternatives (hosts.yaml with auth: password).

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/TMYTiMidlY/portal-mcp-server'

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