Skip to main content
Glama
Sign In
ios-control-mcp

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_list_apps

Lists installed iPhone apps with their bundle identifiers and supports filtering by app name.

Instructions

List installed apps with their bundle identifiers.

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

Input Schema

NameRequiredDescriptionDefault
containsNoFilter on the name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden: it does not state that the operation is read-only, whether results are paginated or complete, or whether the listing covers system apps as well as user apps. 'List' implies non-mutating behavior, but nothing beyond that is conveyed.

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?

One short, front-loaded sentence with no filler or redundant restatement of the title. It is perhaps too terse rather than bloated, which is not a conciseness penalty.

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?

For a one-optional-parameter read tool with no output schema, the description is minimally adequate: it names the return payload (bundle identifiers) so return-value explanation is largely covered. It still omits whether filtering is substring/case-sensitive and whether all installed apps are returned.

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 description coverage is 100% and the single optional 'contains' parameter is documented as 'Filter on the name', so the schema does the work. The description adds nothing about the filter, but baseline 3 applies when coverage is high.

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 gives a specific verb ('List') and object ('installed apps') plus the key payload detail ('with their bundle identifiers'). It is distinguishable from siblings like iphone_list_devices or iphone_wait, though it never explicitly contrasts itself with them.

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 guidance at all — nothing says this is the discovery step before iphone_open_app, nor any prerequisite or restriction. The agent must infer the tool's role purely from the name and the sibling list.

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