Skip to main content
Glama

settings-permissions

Grant, deny, or reset app permissions for testing without opening system settings. Configure permission states for iOS simulator or Android emulator before app requests them.

Instructions

Grant, deny, or reset a runtime permission for an app without navigating the system Settings UI. Use during test setup to pre-authorize (or explicitly deny) a service before the app asks, or reset so the permission dialog appears again on next use. Always per-app: bundleId is required. Permissions: camera, microphone, photos, contacts, notifications, calendar, location, location-always, media-library, motion, reminders. iOS simulator: edits the simulator's TCC store, always per-app. notifications is not supported (no iOS equivalent). reset is per-app — a device-wide reset is a no-op for existing grants on recent iOS, so it is not offered. grant location/location-always needs the app already installed (location auth isn't stored in TCC and isn't applied to a bundle id until the app exists) — enforced on local simulators; a remote simulator can't be probed for install state, so ensure the app is installed there first. Other services can be granted before install. Android: changes the mapped android.permission.* runtime permissions (reset also best-effort clears the user-set permission flags). The app must be installed and declare them in its manifest; reminders has no Android equivalent. Some permission changes terminate the app if it is running (system behavior on both platforms) — set permissions before launching, or relaunch after. Returns { action, permission, bundleId, applied, skipped? }: applied lists the platform-level services/permissions actually changed; skipped (Android) lists mapped permissions the package manager rejected, e.g. ones the manifest doesn't declare. Fails if nothing could be applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYesTarget device id from `list-devices` (iOS simulator UDID or Android serial).
actionYes`grant` pre-authorizes the permission, `deny` refuses it, `reset` returns it to the not-yet-asked state so the app prompts on next use.
bundleIdYesApp to change the permission for — required for every action. iOS: bundle id (e.g. com.example.app). Android: package name. `reset` is per-app too: simctl's device-wide reset (no bundleId) silently leaves existing per-app grants untouched on recent iOS, so the permission is always reset for this one app.
permissionYesThe permission to change. `notifications` is Android-only (iOS has no simctl service for it); `reminders` is iOS-only; `camera` works on Android and on iOS only when the target simulator's runtime models the service (varies by simruntime, not by the installed Xcode).
Behavior5/5

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

With no annotations provided, the description carries full responsibility and excels. It discloses per-app requirement, platform differences (iOS TCC store vs Android permissions), termination of running app on permission change, return format with applied/skipped fields, and failure conditions. This is comprehensive behavioral disclosure.

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 appropriately sized for a complex tool, well-structured with a high-level purpose first, then per-platform details, and finally return value. Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

Given no output schema, the description explains the return value (applied/skipped). It covers all necessary aspects: actions, parameters, platform specifics, error conditions (e.g., failure if nothing applied). The tool is complex, but the description is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant value beyond the schema. For action, it explains per-app reset behavior; for bundleId, it clarifies per-app reset; for permission, it provides platform-specific notes (e.g., notifications Android-only, reminders iOS-only). This extra context is critical for correct usage.

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 starts with a clear statement of what the tool does: 'Grant, deny, or reset a runtime permission for an app without navigating the system Settings UI.' It specifies the verb (grant/deny/reset), resource (runtime permission), and clearly distinguishes the tool from siblings, none of which manage permissions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises use during test setup to pre-authorize or deny permissions before the app asks, or to reset the permission dialog. It covers platform-specific behaviors but does not explicitly state when not to use the tool, though it implies limitations (e.g., notifications unsupported on iOS, app must be installed for location).

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/software-mansion/argent'

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