Skip to main content
Glama

start_session

Spawn a target process on a device and create a Frida session for dynamic instrumentation. Assign a session ID, specify the target package or binary, and optionally set device and spawn arguments.

Instructions

Spawn target on the named device and open a Frida session.

Args: session: analyst-chosen session id. The MCP layer keeps a table mapping session id → live Frida session. Pick something readable (e.g. "android-game"). target: package name (Android), bundle ID (iOS), or absolute path to a native binary. device_id: "usb", "local", "remote:<addr>", or a specific device id. Empty string means the first available device. spawn_args: extra argv to pass to the target on spawn. wait: when True (default), block until the spawned process is unpaused.

Returns::

{
  "status": "OK",
  "session_id": "...",
  "pid": N,
  "device_id": "...",
  "kind": "spawn"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYes
targetYes
device_idNo
spawn_argsNo
waitNo
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: spawning, session creation, parameter effects (especially wait causing blocking), and return format. Could mention session lifecycle or cleanup, but sufficient.

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?

Well-structured with Args section and return example. Somewhat verbose but efficient; every sentence adds value. Could be slightly more concise without losing clarity.

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?

Covers all parameters and return format. For a spawn tool with 5 params and no output schema, it provides sufficient information for correct use. Lacks edge cases or error scenarios, but adequate.

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?

With 0% schema coverage, the description adds substantial meaning: explains session as user-chosen readable id, target as package/bundle/path, device_id formats, spawn_args as extra argv, wait as blocking behavior. Fully compensates for schema gaps.

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 spawns a target on a named device and opens a Frida session. It uses a specific verb ('Spawn') and resource, distinguishing it from siblings like attach_pid.

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 this tool versus alternatives such as attach_pid. The description does not specify prerequisites or exclusions, making it hard for an agent to choose correctly.

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/Heretek-RE/re-frida'

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