Skip to main content
Glama
Sign In
LibXposed MCP Server

LibXposed MCP Server

by Ra1nify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_service_guide

Retrieves LibXposed service guides covering XposedService, RemotePreferences, hot reload, Direct Boot, and AIDL to support Android module development.

Instructions

Get comprehensive guides for libxposed:service, including XposedService, XposedServiceHelper, modern RemotePreferences, HookedTarget process introspection, Hot Reload protocols, Direct Boot rules, and AIDL definitions.

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": {
      "topic": "<topic>"
    },
    "name": "get_service_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesService topic to retrieve: 'xposed_service', 'remote_preferences', 'hot_reload', 'direct_boot', 'aidl', or 'all'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses content scope (service APIs, RemotePreferences, Hot Reload, Direct Boot, AIDL) and the word 'comprehensive' hints at long reference output, but it says nothing about output format, length, pagination, or whether 'all' concatenates every guide — all relevant for a docs-fetch tool.

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 the verb and resource first, followed by the content inventory. The long enumeration is dense but each item plausibly helps an agent judge relevance; there is no filler or repetition.

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 one-parameter, read-only documentation lookup with a fully documented schema and no output schema, this is close to adequate. What is missing is any expectation-setting about the returned guide (format, size, whether 'all' is unwieldy), which matters for an agent deciding between 'all' and a specific topic.

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 topic enum is fully described, so the schema already does the heavy lifting. The description adds topical meaning to some values (e.g., RemotePreferences, Hot Reload, Direct Boot) but never maps each enumerated topic string to its content, leaving ambiguity for 'aidl', 'xposed_service', and 'all'.

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 ('Get') and resource ('comprehensive guides for libxposed:service') and enumerates the covered subject areas, so an agent knows exactly what this returns. It does not explicitly contrast itself with siblings like get_api_doc or get_helper_guide, so the differentiation is only implicit in the topic names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of the alternatives (get_api_doc, get_helper_guide, get_scaffold) that an agent could pick instead. The only signal is the topic enumeration, which implies coverage but not selection criteria.

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