Skip to main content
Glama

renef_resume

Resume a spawn-gated Android process after spawning it, allowing execution to continue for debugging, instrumentation, or Lua-based inspection.

Instructions

Resume a spawn-gated process (after renef_spawn).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the key behavioral trait: this only applies to processes that were spawn-gated via renef_spawn. It says nothing about side effects, idempotency, or what happens if the process is not in a gated state, which leaves meaningful gaps for a state-changing tool.

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?

A single short sentence with the precondition front-loaded in parentheses; nothing is wasted. The only weakness is that the compressed phrasing leans on an undefined term, so brevity costs some 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?

For a zero-parameter tool with an output schema present, the description covers the action and the precondition, and return values need not be explained. It falls short on failure modes and on defining the gating concept, which matter for a process-state operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the schema is complete by construction. Baseline 4 applies.

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?

Specific verb ("Resume") plus a qualified resource ("spawn-gated process"), which distinguishes it from siblings like renef_spawn or renef_exec. The term "spawn-gated" is jargon that an agent may not resolve without prior context, keeping it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "(after renef_spawn)" gives an explicit ordering precondition, which is real when-to-use guidance. It stops there: no statement of when this should not be called, no alternative for restarting a process that was never spawn-gated, and no behavior for repeated calls.

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