Skip to main content
Glama
Sign In
claude-android

claude-android

by duonglkh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_manifest

Parses an AndroidManifest.xml file to extract package name, permissions, application class, and activities. Provide the absolute file path to get structured data.

Instructions

Read AndroidManifest.xml and return parsed structure: package, permissions, application class, activities. Pass manifestPath = absolute path to the AndroidManifest.xml file.

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": {
      "manifestPath": "<manifestPath>"
    },
    "name": "read_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestPathYesAbsolute path to AndroidManifest.xml.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Implies read-only behavior with 'Read and return parsed structure', but no details on error handling, permissions, or side effects. Since no annotations exist, description carries burden but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and return value, then parameter details. No unnecessary words.

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?

For a simple one-parameter read tool without output schema, description covers what it does, what it returns, and the required input. Complete given low complexity.

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 description repeats the schema's description. No additional meaning added beyond what the schema already provides.

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?

Explicitly states the tool reads AndroidManifest.xml and returns a parsed structure including specific elements (package, permissions, etc.). Distinguishes from siblings (get_project_info, read_gradle) by targeting a specific file type.

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?

Provides the required parameter and its format ('absolute path'), but no explicit guidance on when to use this tool over alternatives or conditions to avoid.

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