Skip to main content
Glama

desktop_permissions

Check accessibility, screen recording, and automation permission states, then request missing permissions or open macOS System Settings with an on-screen guide.

Instructions

agent-desktop permissions: Check nested permission states: accessibility/screen_recording/automation each return {state,...}

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

Input Schema

NameRequiredDescriptionDefault
guideNoOpen System Settings with an on-screen guide for granting the missing permissions (macOS)
requestNoRequest missing permissions in the bounded isolated helper

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose the return shape ({state,...} per permission), which is genuinely useful since there is no output schema, but it says nothing about prompting behavior, side effects of the guide/request flags, or whether the check is cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no wasted padding, but the single colon-chained sentence with a literal '{state,...}' fragment is cryptic rather than front-loaded; it reads like an implementation note more than agent-facing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two optional flags, no annotations and no output schema, the definition is barely sufficient: it hints at return structure but does not characterize what permission states exist, what happens when a permission is missing, or what the flags do beyond the schema's own wording.

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 100% and both parameters (guide, request) are fully documented in the schema, so the baseline is 3. The description adds no meaning about these flags or how they interact with the reported permission states.

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 a specific verb ('Check') and resource ('nested permission states') and enumerates exactly which permissions are covered (accessibility/screen_recording/automation). That is concrete enough to distinguish it from the generic sibling desktop_check, though it never explicitly contrasts with it.

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 when-to-use or when-not-to-use guidance. An agent cannot tell from the description whether this is the prerequisite call before desktop automation actions or how it relates to desktop_check; nothing indicates it should be run before attempting actions that need those permissions.

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