Skip to main content
Glama

renef_status

Verifies the full Android connection chain—ADB device, port forward, server ping/pong, and active target session—so you can diagnose setup issues before instrumentation.

Instructions

Check the whole chain: adb device, adb port forward, renef_server reachability (ping/pong), and active target session. Start here.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the four things verified (device, port forward, server reachability, session), but says nothing about failure semantics — whether checks short-circuit on the first failure, how long they take, or whether any step has side effects.

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?

A single front-loaded sentence plus a two-word call to action. Every clause lists a distinct check and the ordering advice is placed at the end where it is most actionable.

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 diagnostic with an output schema covering return values, the description is nearly complete: it tells the agent what is verified and that this is the entry point. The only material gap is how partial failures are reported, which the output schema may partly cover.

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 nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% and the empty argument object matches the description's no-input framing.

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?

Names a specific verb ('Check') and enumerates the exact chain being inspected: adb device, adb port forward, renef_server ping/pong, and active target session. An agent can tell this is a diagnostic/health tool rather than a control action like renef_server_start or renef_attach, though it doesn't name 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 Guidelines4/5

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

'Start here' gives clear entry-point sequencing guidance, which is the key usage signal for a status tool. It stops short of stating when NOT to use it or naming the specific sibling to call after a failed check, so it's clear context without explicit exclusions.

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