Skip to main content
Glama
Sign In
sandbox-mcp

sandbox-mcp

by bird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

children

Show all subordinate sandboxes of a specified parent. Displays status for each or indicates when none exist.

Instructions

List all child sandboxes of a parent.

Args: parent: Name of the parent sandbox.

Returns: List of children with status, or indication that none exist.

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

Input Schema

NameRequiredDescriptionDefault
parentNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the function and return type, but does not disclose any behavioral traits such as side effects, authentication needs, or error conditions.

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 concise with a front-loaded main sentence. The Args and Returns sections add minimal value but are not overly verbose. Could be slightly tighter.

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?

The tool is simple with one parameter and an output schema (not shown). The description provides basic functionality and return type, but lacks examples or elaboration on what constitutes a 'child sandbox' context.

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

Parameters3/5

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

The description adds 'Name of the parent sandbox' for the 'parent' parameter, which provides context beyond the schema's default and title. However, schema coverage is 0% and the description does not clarify the optional nature or default value.

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?

The description clearly states 'List all child sandboxes of a parent.' It uses a specific verb ('List') and resource ('child sandboxes'), and the context of 'parent' distinguishes it from siblings like list_all or status.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It does not specify prerequisites, exclusions, or scenarios where another tool would be more appropriate.

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