Skip to main content
Glama

renef_list_apps

Lists installed Android packages on a connected device via adb without a session, with an option to show only third-party apps by skipping system packages.

Instructions

List installed packages on the device (via adb, no session needed). Set third_party_only=true to skip system packages.

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

Input Schema

NameRequiredDescriptionDefault
third_party_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the mechanism (adb) and the session-independence constraint, which are genuinely useful behavioral facts. It does not cover failure modes (no device connected, adb authorization) or whether the call is slow, leaving meaningful gaps for a device-touching tool.

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?

Two short sentences, no filler, with the resource and the key operational caveat front-loaded and the parameter hint second. Every clause earns its place.

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?

For a one-optional-parameter read-only listing tool with an output schema present, the description covers mechanism, session requirement, and filter semantics. Return values are documented by the output schema, so nothing essential is missing.

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?

Schema description coverage is 0%, so the description must compensate, and it does by explaining the single parameter's effect: third_party_only=true skips system packages. This tells the agent exactly what true versus default false returns, which the schema alone (title/default only) does not.

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 names a specific verb and resource ("List installed packages on the device") and indicates the transport ("via adb"). This is clearly distinct from siblings such as renef_list_processes or renef_list_hooks, though it does not explicitly contrast itself with them.

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?

"no session needed" gives real routing context in a toolset where most siblings require an attached session, telling the agent this can be called standalone. It stops short of explicitly naming alternatives or stating exclusions, so it is clear context rather than full when/when-not guidance.

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