apk-docforge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_appsA | Search allowed app sources without downloading, then persist candidates locally. |
| download_appC | Download a persisted allowed candidate by numeric candidate id with quarantine and provenance. |
| analyze_artifactC | Run static apk-docforge analysis for a local APK/APKS/XAPK artifact. |
| get_analysisC | Get analysis summary and output paths by analysis id or database id. |
| get_reportB | Get the Markdown report for an analysis. |
| get_codex_promptC | Get the generated Codex ingestion prompt for an analysis. |
| list_findingsB | List security findings for an analysis. |
| list_featuresB | List inferred and observed features for an analysis. |
| list_screensC | List static screens mapped for an analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct stage or artifact: search/download handle acquisition, analyze_artifact creates the analysis, and the get/list tools expose distinct outputs such as findings, features, screens, reports, or prompts. There are no overlapping tool purposes that would confuse an agent.
All tool names follow a consistent verb_noun pattern: search_*, download_*, analyze_*, get_*, and list_*. The get_ vs list_ split is also consistent: get_ returns a single item or document, while list_ returns a collection.
Nine tools is an appropriate size for an APK analysis pipeline. Every tool maps to a distinct workflow step or output artifact, and none feel redundant or extraneous.
The pipeline covers the full lifecycle needed for APK docforge work: search, download, analysis, report generation, prompt generation, and detailed findings/feature/screen listings. The only minor gap is the absence of a general list_analyses or candidate-management tool, which could limit discoverability but does not break the core workflow.