Skip to main content
Glama

renef_server_deploy

Push the renef_server and agent library to a rooted Android device, set permissions and SELinux context, and verify transfer integrity via md5 checksum.

Instructions

Push the built renef_server + libagent.so to the device, set permissions and the SELinux context the agent needs, and verify by md5. source="auto" (default): prefer a local build (RENEF_BIN_DIR, else <RENEF_HOME>/build/android); if none exists, download the pinned CI-built binaries from this package's GitHub release and SHA256-verify them. source="build": require the local build. source="download": always download.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoauto

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the real side effects: writing binaries to the device, mutating file permissions and SELinux context, and an md5 self-check. It does not say whether an existing server is stopped/overwritten or what happens if the device is unreachable, but the core mutation profile is disclosed.

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?

Front-loaded with the action and effect, then the parameter modes in decreasing order of importance; nearly every clause carries information. The mid-sentence line break after 'permissions' and the dense run-on in the auto-mode clause slightly hurt readability.

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

Completeness5/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 no explanation, and the one parameter is exhaustively documented along with the tool's on-device effects. What remains absent (prerequisites such as an active connection) is minor against this coverage.

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?

Schema coverage is 0% and `source` has no enum in the schema, yet the description defines all three modes (auto/build/download) including the default, the RENEF_BIN_DIR and <RENEF_HOME>/build/android lookup order, and the SHA256-verified download fallback. This fully compensates for the empty schema.

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?

States a concrete verb+resource chain: pushes renef_server and libagent.so, sets permissions and SELinux context, verifies by md5. This is clearly distinct from the sibling lifecycle tools (start/stop/restart/logs), which operate on an already-deployed server.

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 description spends most of its guidance on source-mode selection, which is genuinely useful, but never states the tool-level context: when to deploy versus re-deploy, or whether the device must be attached first. Usage is implied by the artifact-transfer framing rather than stated as a condition.

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