Skip to main content
Glama
Sign In
ios-agent-driver

ios-agent-driver

by CodeJonesW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_permission

Control app privacy permissions on iOS simulators: grant, revoke, or reset access to photos, camera, location, notifications, and more.

Instructions

Grant/revoke/reset a privacy permission for an app (e.g. photos, camera, location, notifications).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "service": "<service>",
      "bundle_id": "<bundle_id>"
    },
    "name": "set_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
serviceYese.g. all, photos, camera, location, notifications, contacts, microphone
bundle_idYes
udidNoTarget simulator UDID. Defaults to the booted sim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description does not disclose side effects, whether changes are immediate, scope of reset, or error states. Does not clarify behavior when app is not installed.

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?

Single sentence, clear and front-loaded. No redundant information, though could expand slightly without waste.

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

Completeness2/5

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

Missing context about simulator environment (udid), return behavior, and implications of changes. For a tool with 4 parameters and no output schema, description is too sparse.

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 50%. Description adds example services (photos, camera) already in schema. No extra meaning for bundle_id or udid beyond schema. Acceptable but not compensative.

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 tool grants, revokes, or resets privacy permissions for apps, listing example services. It uses specific verbs and distinguishes from sibling tools like deeplink or install_app.

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?

No guidance on when to use grant vs revoke vs reset, or prerequisites for the app or simulator. Does not mention alternatives or exclusions.

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

Deploy Server

Other Tools