Skip to main content
Glama
Sign In
LibXposed MCP Server

LibXposed MCP Server

by Ra1nify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_helper_guide

Retrieve guides and API references for libxposed:helper topics, including HookBuilder fluent discovery, Reflector caching, and Kotlin DSL extensions.

Instructions

Get comprehensive guides and API references for libxposed:helper, including HookBuilder fluent discovery, Reflector reflection utilities, and Kotlin helper-ktx DSL.

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_helper_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic to retrieve: 'hook_builder' for fluent discovery, 'reflector' for reflection caching, 'kotlin_dsl' for Kotlin extensions, or 'all'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 full behavioral disclosure. It implies a static read that returns documentation, which is inherently low risk, and the word 'comprehensive' hints at a large payload. It does not state output format, size, whether the payload is static or versioned, or how 'all' differs from per-topic retrieval, leaving moderate gaps for a no-annotation 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?

It is one front-loaded sentence that names the resource and then enumerates the covered topics, with no structural waste. The adjective 'comprehensive' is slightly promotional filler, but overall it is efficiently sized for a simple single-parameter lookup tool.

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?

For a one-parameter documentation lookup with 100% schema coverage and no output schema, the description covers what the tool returns at a topic level. The missing piece is the boundary against get_api_doc and get_service_guide, which matters given how similar those siblings are.

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% and the single topic parameter has a full enum description, so the baseline is 3. The description loosely mirrors three of the four enum values ('HookBuilder fluent discovery', 'Reflector reflection utilities', 'Kotlin helper-ktx DSL') but adds no detail beyond them and never mentions the 'all' option.

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?

The description uses a specific verb plus resource (get guides and API references for libxposed:helper) and enumerates the three content areas: HookBuilder fluent discovery, Reflector reflection utilities, and the Kotlin helper-ktx DSL. This is much clearer than a bare name. However, it never distinguishes this tool from close siblings such as get_api_doc and get_service_guide, so an agent cannot tell which one to call when it needs helper documentation.

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: the agent infers it should call this when it needs libxposed:helper documentation. There is no explicit when-to-use statement, no prerequisite, and no exclusion naming get_api_doc or get_service_guide as alternatives. Given that those siblings plainly overlap in scope, the missing differentiation is a real gap.

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