Skip to main content
Glama

check_permissions

Read-only

Verify macOS Accessibility and Screen Recording permissions for desktop automation. Returns status and setup instructions for missing permissions.

Instructions

Check whether macOS Accessibility and Screen Recording permissions are granted. Returns status for each permission and instructions for any that are missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'check_permissions' tool which tests Accessibility and Screen Recording permissions.
    async function handleCheckPermissions(): Promise<CallToolResult> {
      const accessibility = await testAccessibility();
      const screenRecording = await testScreenRecording();
    
      const missing: string[] = [];
      if (!accessibility) missing.push(ACCESSIBILITY_INSTRUCTIONS);
      if (!screenRecording) missing.push(SCREEN_RECORDING_INSTRUCTIONS);
    
      const instructions =
        missing.length === 0
          ? "All permissions granted."
          : `Grant the following permissions:\n${missing.map((m) => `  - ${m}`).join("\n")}`;
    
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(
              { accessibility, screenRecording, instructions },
              null,
              2,
            ),
          },
        ],
      };
    }
  • Input schema definition for the 'check_permissions' tool.
    const CheckPermissionsInputSchema = z.object({});
  • MCP tool definition for 'check_permissions' in utilityToolDefinitions array.
    {
      name: "check_permissions",
      description:
        "Check whether macOS Accessibility and Screen Recording permissions are granted. Returns status for each permission and instructions for any that are missing.",
      inputSchema: zodToToolInputSchema(CheckPermissionsInputSchema),
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • Registration of the 'check_permissions' handler in the tool dispatch map.
    check_permissions: () => enqueue(() => handleCheckPermissions()),
Behavior4/5

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

Annotations indicate read-only and non-destructive behavior, which the description aligns with by describing a check operation. The description adds value beyond annotations by specifying the return content ('status for each permission and instructions for any that are missing'), providing useful context about output behavior that annotations do not cover.

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, well-structured sentence that efficiently conveys the tool's purpose, action, and return value without any wasted words. It is front-loaded with the core function and provides complete information in a concise manner.

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?

Given the tool's simplicity (0 parameters, read-only, non-destructive) and lack of an output schema, the description is nearly complete. It explains what the tool does and what it returns, though it could slightly enhance completeness by mentioning potential error cases or system dependencies, but this is minor.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description does not need to explain parameters, and it appropriately focuses on the tool's function and output, adding no unnecessary parameter information.

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 clearly states the specific action ('Check') and target resources ('macOS Accessibility and Screen Recording permissions'), distinguishing it from sibling tools that perform UI automation or system interaction tasks. It explicitly mentions what is returned ('status for each permission and instructions for any that are missing'), making the purpose unambiguous.

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 usage in contexts where permission status is needed, such as before performing actions that require these permissions. However, it does not explicitly state when to use this tool versus alternatives (e.g., which sibling tools might depend on these permissions) or provide exclusions, leaving some guidance to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/antbotlab/mac-use-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server