Skip to main content
Glama
Sign In
sandbox-mcp

sandbox-mcp

by bird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stats

Check CPU, memory, and disk usage of an active sandbox. Specify the sandbox name to monitor its resource consumption.

Instructions

Show resource usage (CPU, memory, disk) of the active sandbox.

Args: sandbox: Named sandbox to check (default "default")

Returns: Current resource usage statistics.

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

Input Schema

NameRequiredDescriptionDefault
sandboxNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so description carries the burden. It states it shows resource usage (read-only), but doesn't disclose error behavior, auth needs, or limitations beyond the sandbox parameter.

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?

Short and front-loaded with the main purpose. Args and Returns sections provide structure without unnecessary text. Only essential information is included.

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?

Tool is simple with one optional parameter. The description covers the resource types and argument. Output schema exists, so return details aren't needed. Adequate for the tool's complexity.

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?

Schema coverage is 0%, but the Args section adds meaning: 'sandbox: Named sandbox to check (default "default")'. This explains the parameter's purpose beyond type and default, though no valid values or constraints are given.

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 the tool shows resource usage (CPU, memory, disk) of the active sandbox. It uses a specific verb and resource, distinguishing it from siblings like 'health' or 'status', though not explicitly.

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 versus alternatives (e.g., 'health', 'status') is provided. The description only explains what it does, not the context or prerequisites.

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