Skip to main content
Glama

Describe the sandbox

lugh_sandbox
Read-onlyIdempotent

Lists simulated files, HTTP endpoints, MCP servers and shell commands available to programs run by lugh_run, showing each allowed action before execution.

Instructions

List the simulated files, HTTP endpoints, MCP servers (with each tool's effect) and shell commands that programs run by lugh_run can use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: it discloses that the resources are simulated/sandboxed and that MCP server listings include each tool's effect, which tells the agent what level of detail to expect. It does not describe the output format or size, leaving a small gap.

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?

A single front-loaded sentence beginning with the verb 'List', with no filler or redundancy. Every clause names a distinct class of resource that will be returned.

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 zero-parameter, read-only discovery tool with no output schema, the description covers what is enumerated and ties it to lugh_run. The only omission is any hint about how the listing is returned (format, length, whether it can be large), which is minor at this complexity.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing parameters or filters.

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 gives a specific verb ("List") and a precise set of resources: simulated files, HTTP endpoints, MCP servers with per-tool effects, and shell commands. It also anchors the resource to lugh_run's programs, which separates it from lugh_run/lugh_check. It stops short of distinguishing itself from lugh_reference, another likely documentation-style sibling, so a 4 rather than a 5.

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?

Usage is implied by the phrasing 'that programs run by lugh_run can use' — an agent can infer this is a discovery step to consult before or while writing a program. There is no explicit 'use this when' instruction and no exclusions or named alternatives, so guidance remains implicit rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.