Skip to main content
Glama

search_classes_by_keyword

Search decompiled Android code for classes matching a keyword, with options to filter by package and search in class names, methods, fields, code, or comments.

Instructions

Search for classes containing a specific keyword with flexible filtering options.

This tool performs a comprehensive search across decompiled Android code, allowing you to:

  1. Search within specific packages by providing a package name

  2. Target specific search scopes (class names, method names, fields, code content, comments)

  3. Combine multiple search scopes for precise results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_termYesThe keyword or string to search for. This is the main search query.
packageNoPackage name to limit the search scope. - If empty string (default), searches across all packages in the APK - If provided, only searches within classes belonging to the specified package - Example: "com.example.app" to search only in that package
search_inNoComma-separated list of search scopes to target. Valid values: - "class": Search in class names only - "method": Search in method names only - "field": Search in field names only - "code": Search in code content (method bodies, statements, etc.) - "comment": Search in comments You can specify one or multiple scopes: - Single scope: "class" (only class names) - Multiple scopes: "class,method" (class names OR method names) - Combined: "class,method,code" (searches in all three scopes) Default: "code" (searches in code content)code
offsetNoStarting index for pagination. Default: 0
countNoMaximum number of results to return. Default: 20

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries burden. Describes search behavior and filtering but does not explicitly state that the tool is read-only or non-destructive. Assumed safe but not confirmed.

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?

Description is a well-structured paragraph with clear numbered points, concise but covers essential aspects. No fluff, but could be slightly more compact.

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

Completeness5/5

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

Given the tool's complexity (keyword search, package filtering, multiple scopes, pagination) and presence of output schema, the description fully covers what the tool does and its parameters. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all parameters (100% coverage). Description adds value by explaining how parameters combine (e.g., 'combine multiple search scopes for precise results'), providing context beyond schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states 'Search for classes containing a specific keyword', clearly specifying the action and resource. It distinguishes from siblings like search_method_by_name and get_all_classes by focusing on keyword-based class search across decompiled code.

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?

Description lists capabilities but does not explicitly state when to use this tool versus alternatives. Usage is implied but no clear 'when not to use' or comparison with sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zinja-coder/jadx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server