Skip to main content
Glama
Sign In
declaw-mcp-server

declaw-mcp-server

Official
by declaw-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_sandboxes

List all active sandboxes tied to your API key, giving you a clear view of your running secure code execution environments.

Instructions

List all active sandboxes for the current API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly indicates a non-destructive list operation and adds context about 'active' status and 'current API key'. However, it does not disclose details like pagination, sort order, or the structure of the returned objects, which could matter for a complete behavioral picture.

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 a single, front-loaded sentence that states the verb, resource, and scope. Every word earns its place, with no redundancy or filler.

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?

For a simple list operation with no parameters and no output schema, the description adequately conveys the core purpose and scope. It could mention return value structure, but given the simplicity and the sibling tool set, it is reasonably complete. A minor gap is not specifying what fields will be returned for each sandbox.

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 tool has zero parameters, and the input schema is empty. According to the rubric, a zero-parameter tool deserves a baseline of 4. The description adds no parameter information, but none is needed since there are no parameters.

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 uses the specific verb 'List' with a clear resource ('sandboxes') and scope ('all active sandboxes for the current API key'). This clearly distinguishes it from sibling tools like create_sandbox, kill_sandbox, and file/list operations.

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

Usage Guidelines3/5

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

The description implies its use for retrieving a user's active sandboxes, and the context of 'current API key' adds a filtering condition. However, it does not explicitly mention when to use it instead of alternatives, nor does it state any exclusions 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