frida-ios-mcp

Overview Schema Source Related Servers Discussions Admin

session_close

Close an iOS app session, and by default also close SpringBoard and Photos. Keep either alive using closeSpringBoard or closePhotos flags.

Instructions

Close app session. Default also closes SpringBoard and clears Photos side channel (photosAlive). closeSpringBoard=false keeps SB; closePhotos=false keeps Photos.

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

Input Schema

Name	Required	Description	Default
`closePhotos`	No	Default true. false = leave Photos.app channel alive.
`closeSpringBoard`	No	Default true. false = keep SpringBoard for later (intentional, not an error).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

A3.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains default closing of SpringBoard and Photos side channel, and how parameters modify behavior. However, it does not disclose potential side effects like data loss or session state after closing.

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?

Description is a single, front-loaded sentence that efficiently conveys the core behavior and parameter effects without unnecessary words.

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?

While the description covers basic behavior and parameter effects, it omits prerequisites (e.g., session must be open), error conditions, return values, and whether the tool is destructive. Given no output schema, more context would be helpful.

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%—both parameters already have descriptions. The description reiterates defaults without adding new information beyond the schema, so it provides minimal added value.

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?

Clearly states 'Close app session' with specific verb and resource, and lists default behaviors. However, it does not distinguish from sibling session tools like session_respawn or session_force_unlock, which would help an agent choose correctly.

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 explicit guidance on when to use this tool versus alternatives such as session_respawn or session_force_unlock. The description implies closing a session, but lacks context about appropriate scenarios or prerequisites.

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