Skip to main content
Glama
TMYTiMidlY

portal-mcp-server

by TMYTiMidlY

portal_tunnel

Open, close, or list SSH tunnels. Supports local port forwarding, reverse tunnels, and SOCKS5 proxy through a single host.

Instructions

Manage SSH tunnels — a single entry point (like portal_host) where action selects the operation and the other args parameterise it.

Actions

  • action="open": open a tunnel through host. kind picks the type:

    • kind="local" : forward localhost:local_port → remote_host:remote_port via host. Required: remote_host, remote_port (local_port 0 = auto). Example: portal_tunnel(action="open", kind="local", host="bastion", local_port=5432, remote_host="db.internal", remote_port=5432)

    • kind="reverse": expose local_bind:local_port to host as host:remote_port. Required: remote_port, local_bind, local_port. Example: portal_tunnel(action="open", kind="reverse", host="bastion", remote_port=8080, local_bind="127.0.0.1", local_port=3000)

    • kind="socks" : SOCKS5 proxy on localhost:local_port via host. Required: local_port (default 1080). Example: portal_tunnel(action="open", kind="socks", host="bastion", local_port=1080)

    Returns {tunnel_id, type, host, local, remote}.

  • action="close": close a live tunnel. Required: tunnel_id (from open). Example: portal_tunnel(action="close", tunnel_id="ab12cd34")

  • action="list": list all active tunnels (JSON array).

Tunnels are a resource you manage explicitly (open → close), so list lives here rather than in portal_audit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNo
kindNolocal
actionYes
tunnel_idNo
local_bindNo127.0.0.1
local_portNo
remote_hostNo
remote_portNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully carries the burden. It details the behavior of each action, specifies return values for 'open' and 'list' outputs, and notes explicit lifecycle management. It lacks mention of potential side effects like timeouts or authentication requirements, which would push it to a 5.

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?

The description is well-structured with sections and examples, front-loading the purpose. It is somewhat lengthy but every sentence adds value. Minor tightening could be done, but it remains scannable.

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?

Given 8 parameters, 3 actions, no annotations, and an output schema (not provided), the description is quite complete. It covers all actions, parameter requirements, examples, and return types. Missing error handling or detailed return format, but the output schema likely covers that.

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 0% description coverage, but the description compensates by explaining each parameter in the context of actions with examples. While not all parameters are individually defined, the action-specific usage clarifies their meaning sufficiently.

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 clearly states the tool manages SSH tunnels with specific actions (open, close, list). It distinguishes from sibling tools by noting that 'list' belongs here rather than in portal_audit.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use each action, including required parameters and examples. It mentions that tunnels are managed explicitly (open → close), but does not elaborate on when not to use this tool or provide detailed alternatives beyond the single sibling mention.

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