LibXposed MCP Server

get_api_doc

Retrieve LibXposed core API documentation, including method signatures, parameters, return types, sinceApi versions, and Javadoc links to check usage and compatibility.

Instructions

Retrieve detailed documentation, method signatures, parameters, return types, sinceApi version, and official Javadoc links for LibXposed core API classes.

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": {
      "className": "<className>"
    },
    "name": "get_api_doc"
  }
}

Input Schema

Name	Required	Description	Default
`className`	Yes	Name of the class or interface (e.g., 'XposedInterface', 'XposedModule', 'Chain', 'Hooker', 'Invoker', 'HookHandle', 'HookBuilder')
`memberName`	No	Optional method or constant name to focus on (e.g., 'hook', 'deoptimize', 'proceed', 'replaceHook', 'API_102')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.5/5.0

Behavior3/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 does good work describing the returned content (signatures, return types, sinceApi version, Javadoc links), making the read-only lookup nature evident, but it says nothing about behavior on an unknown className, whether the result is scoped by memberName, or any failure mode.

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?

A single front-loaded sentence with no filler; the enumeration of returned fields is dense but each item carries information. Slightly list-like phrasing rather than flowing prose keeps it from a 5.

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?

There is no output schema, so the description must describe return values and it does so concretely (method signatures, parameters, return types, sinceApi, Javadoc links). Combined with full schema coverage for both parameters, an agent has enough to call it correctly; only error/empty-result behavior is unaddressed.

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%, including examples for both className and the optional memberName, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema states and never mentions the optional narrowing parameter.

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?

Specific verb ("Retrieve") plus a concrete resource ("documentation for LibXposed core API classes"), and it enumerates the payload (signatures, parameters, return types, sinceApi, Javadoc links) so an agent knows exactly what it yields. It does not name a sibling or state how it differs from search_libxposed, so it falls short of 5.

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 the tool for looking up a known class/member, while search_libxposed would be for discovery. There is no explicit when-to-use, no exclusion, and no routing to alternatives despite six siblings being present.

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

Deploy Server