Skip to main content
Glama

sandbox_inspect_policy

Read-onlyIdempotent

Inspect the active sandbox security policy, resource limits, capability flags, allowed binaries, and runtime RED telemetry metrics to verify agent execution constraints.

Instructions

Inspect the active sandbox security policy, resource limits, capability flags, allowed binaries, and runtime RED telemetry metrics.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 the safety profile is covered. The description adds value by disclosing the actual payload contents (policy, limits, capability flags, allowed binaries, telemetry), which is meaningful for a tool with no output schema. It stops short of explaining what the telemetry fields mean or whether results are cached/snapshotted.

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 sentence with no filler, front-loaded with the verb and resource, then the enumerated outputs. Every clause earns its place by naming a distinct piece of returned information.

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 tool with no output schema, the description adequately previews return contents, which is the main thing an agent needs. The one gap is that "RED telemetry metrics" is unexplained jargon, so an agent cannot anticipate the shape or units of that portion of the response.

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 no parameter meaning to explain and the baseline of 4 applies. The empty schema with additionalProperties=false is consistent with the description, which implies a fixed, argument-free inspection call.

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?

Specific verb ("Inspect") plus specific resource ("the active sandbox security policy"), followed by an enumeration of exactly what facets are surfaced: resource limits, capability flags, allowed binaries, and RED telemetry. This is clearly distinguishable from the exec_* and fs_* siblings, which act on the sandbox rather than report on it.

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 only implied: an agent can infer this is the pre-flight/introspection call to make before executing commands, but the description never states when to call it, when not to, or how it relates to exec_command or the fs_* tools. No prerequisites or ordering guidance are given.

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