LibXposed MCP Server

get_scaffold

Generate standard project scaffolds and configurations for LibXposed modules, including Gradle build files, AndroidManifest, ProGuard/R8 rules, entry lists, and Java/Kotlin skeletons.

Instructions

Generate standard project scaffolds and configurations for LibXposed modules, including build.gradle.kts, AndroidManifest.xml, ProGuard/R8 rules, entry list, and Java/Kotlin module skeletons.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "get_scaffold"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes	Type of configuration or code scaffold to generate

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

B3.2/5.0

Behavior2/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 never says whether generated scaffolds are written to disk or returned as content, whether existing files are overwritten, or whether the operation is idempotent — all critical for a 'Generate' tool. Listing the artifact types is the only behavioral signal provided.

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?

One front-loaded sentence that leads with the verb and resource, then enumerates outputs. Slightly redundant wording ('standard project scaffolds and configurations') but nothing that fails to earn its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter generator with no output schema and no annotations, the description should at minimum indicate the return shape or file-writing behavior. It covers what gets generated but leaves the agent guessing about the result and side effects.

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 coverage is 100% and the single enum parameter is documented in the schema, so the baseline is 3. The description's list of artifacts (build.gradle.kts, AndroidManifest.xml, ProGuard/R8, entry list, Java/Kotlin modules) loosely maps to the enum values, adding marginal interpretive value but no detail on how 'all' behaves.

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?

States a specific verb ('Generate') and resource ('project scaffolds and configurations for LibXposed modules') and enumerates the concrete artifacts produced. This clearly separates it from the sibling retrieval tools (get_api_doc, search_libxposed) and from migrate_legacy_code, though it never names those alternatives explicitly.

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?

Usage is only implied: an agent can infer this is for bootstrapping a new LibXposed module, but there is no explicit when-to-use statement, no mention of prerequisites, and no guidance on when to prefer migrate_legacy_code or the guide tools instead.

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

Deploy Server