Skip to main content
Glama

renef_spawn

Spawns an Android app by package name, pauses it at startup via ptrace, and injects the agent; the first exec auto-resumes it, or resume without running a script.

Instructions

Spawn an app by package name, gated at startup (ptrace pause), inject the agent. The first renef_exec auto-resumes the gated process; renef_resume resumes it without running a script.

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": {
      "package": "<package>"
    },
    "name": "renef_spawn"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does reveal the important side effect that the target is paused at startup and stays gated until resumed. It omits prerequisites (privilege level, whether a server/agent deployment must already exist), what happens if the package is already running, and failure behavior, which are material for a mutation-style operation.

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?

Two tight sentences, front-loaded with the action and gate mechanics before the sibling-resume detail; every clause carries information. Slightly compressed phrasing ("inject the agent") assumes context the reader may not have.

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?

An output schema exists, so return values need not be explained, and the description covers the core mechanics and the critical paused-state consequence. Missing detail on preconditions and error cases keeps it from being fully complete for a security-sensitive spawn operation.

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 0% for the single `package` parameter, so the description must compensate; "by package name" clarifies the expected value is an app package identifier rather than a PID or path. It adds only minimal meaning, giving no format example or resolution behavior for an invalid/ambiguous package.

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 names a specific verb and resource ("Spawn an app by package name") and adds the concrete mechanism (gated at startup via ptrace pause, agent injected). It also distinguishes its lifecycle position from renef_exec and renef_resume, so an agent can pick it apart from siblings without opening a schema.

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?

It gives clear downstream context: the first renef_exec auto-resumes the gated process while renef_resume resumes it without running a script, which tells the agent what to call next. It stops short of stating when to choose spawn over renef_attach (e.g., app not yet running vs already running), so no explicit exclusion exists.

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