Skip to main content
Glama
Sign In
sandbox-mcp

sandbox-mcp

by bird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

expose

Create a local TCP proxy that forwards a sandbox port to localhost, enabling local connections to services inside the sandbox.

Instructions

Forward a sandbox port to localhost via TCP proxy. Creates a local listener that proxies connections into the sandbox via container exec.

Args: port: Port number inside the sandbox (e.g., 8000, 3000, 5432). host_port: Port to listen on locally (default: same as sandbox port). sandbox: Named sandbox to expose (default "default").

Returns: Connection URL if successful, or error message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "port": "<port>"
    },
    "name": "expose"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
host_portNo
sandboxNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose all behavioral traits. It explains the mechanism (creates a local listener via container exec) but does not detail side effects like port conflicts, reversibility (use unexpose), or security implications. Adequate but not exhaustive.

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 concise and well-structured, with a one-line purpose statement, a brief mechanism explanation, and a clear Args section listing parameters. Every sentence adds value with no wasted words.

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 the tool's low complexity (3 parameters, simple return value), the description is largely complete. It mentions the return type (connection URL or error). However, it lacks details on error scenarios or prerequisites (e.g., running sandbox). Slight gap but still effective.

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 description coverage is 0%, meaning the JSON schema provides no parameter descriptions. The tool's description compensates fully by explaining each parameter: port (required, integer), host_port (default same as port), and sandbox (default 'default'). This adds essential meaning beyond the 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?

The description clearly states the tool's purpose: 'Forward a sandbox port to localhost via TCP proxy.' It specifies the verb (forward), resource (sandbox port), and mechanism (TCP proxy via container exec). This distinguishes it from siblings like 'unexpose' which reverses the operation.

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 explains when to use the tool (to expose a sandbox port locally) but does not explicitly state when not to use it or mention alternatives. The sibling 'unexpose' implies a complementary use, but no exclusions are given. Still, context is clear enough for most agents.

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