Skip to main content
Glama

renef_attach

Attaches to a running Android process by PID and injects the Renef agent, enabling instrumentation and dynamic analysis of that process.

Instructions

Attach to a running process and inject the renef agent.

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": {
      "pid": "<pid>"
    },
    "name": "renef_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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 behavioral burden, yet it only says an agent is injected. It does not disclose whether injection requires elevated privileges, whether it fails if already attached, whether the target is modified persistently, or that renef_disconnect is the counterpart. For an invasive operation on a live process, this is a significant gap.

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 front-loaded sentence with no filler, and the action and target are stated first. It is efficient, though its brevity is part of why behavioral detail is missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a process-injection tool with no annotations the description should cover prerequisites, side effects, and the relationship to renef_disconnect. None of that is present, leaving the agent under-informed before a potentially destructive call.

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 pid parameter, so the description must compensate. 'Attach to a running process' implies pid identifies the target process, which is minimal but sufficient meaning; it adds no detail on format, validity, or how to discover a pid.

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 states a specific verb and resource: 'Attach to a running process and inject the renef agent.' This distinguishes it from renef_spawn (which would create a new process) and renef_disconnect, though it never names those siblings explicitly.

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 explicit when-to-use guidance, no mention of prerequisites such as obtaining a pid via renef_list_processes, and no statement about when to prefer renef_spawn instead. The only guidance is implicit in the phrase 'running process'.

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