Skip to main content
Glama
Sign In
devilge

devilge

by Yercko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect installed packages

devilge_inspect_packages
Read-onlyIdempotent

Lists installed Android applicationIds with optional substring filter, indicating if a process is running and its PID to help find the correct packageName for error capture.

Instructions

Lists Android applicationIds installed on the device, optionally filtered by a substring. For each match, reports whether a process is currently running and its PID. Use this to discover the right packageName value before calling devilge_get_app_errors.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSubstring filter (e.g. "myapp", "staging", "com.example"). Empty returns up to maxResults installed packages.
serialNoDevice serial. Defaults to DEVILGE_DEFAULT_DEVICE_SERIAL or the only attached device.
maxResultsNoMaximum results to return. Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and non-destructive, so the tool's safety is clear. The description adds value by explaining the output includes process running status and PID, which is not in annotations.

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 sentences, front-loaded with the primary action, followed by a practical usage hint. No superfluous text.

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?

The description explains the main output (process status and PID) but does not detail the format or structure. Given no output schema, a bit more detail would enhance completeness, but it is still sufficient for an agent.

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 100% with well-documented parameters. The description does not add significant meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states it lists installed Android applicationIds with optional filtering and reports process status and PID. It distinguishes itself by explicitly positioning the tool as a prerequisite for devilge_get_app_errors.

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?

The description explicitly recommends using this tool to discover the packageName before calling devilge_get_app_errors. While it does not list exclusions, this guidance is clear and actionable.

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

Deploy Server

Other Tools