Skip to main content
Glama

Show the fence's status

status
Read-only

Check whether the macOS sandbox fence is active and what it protects, plus the policy in force, sessions, and daily fenced, unsandboxed, and refused call counts.

Instructions

Whether the fence (the macOS sandbox) works on this Mac and what it protects, the policy in force, sessions, and calls per day (fenced, unsandboxed, refused).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the returned breakdown (fenced vs unsandboxed vs refused calls, policy in force), which annotations cannot convey; however it says nothing about cost, latency, or whether it probes the environment actively.

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?

A single dense sentence with the core concept ("the fence") front-loaded and immediately defined. Slightly list-like toward the end, but no sentence is wasted.

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 diagnostic with no output schema, the description covers enough of the return surface (health, policy, sessions, call counts by category) for an agent to decide whether to call it. Minor gaps: it does not say whether this only works on macOS or what happens on other platforms.

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 no parameters at all (0 params, empty schema), so there is nothing the description needs to disambiguate. Baseline 4 applies.

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 names the resource ("the fence", explicitly glossed as the macOS sandbox) and enumerates what the tool reports: health on this Mac, what it protects, the policy in force, sessions, and per-day call counts. The verb is carried only by the title ("Show"), and no sibling is named as a contrast, but the diagnostic intent is unmistakable and distinct from file/session/notification siblings.

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?

There is no explicit when-to-use guidance, no precondition such as "call this first to check whether fenced execution is available", and no statement of when not to use it. Usage must be inferred entirely from the content list.

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