Skip to main content
Glama
Sign In
claude-android

claude-android

by duonglkh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_gradle

Parses a Gradle module's build.gradle.kts to extract plugins, Android configuration, and dependencies for analysis.

Instructions

Read a module's build.gradle.kts and return parsed structure: plugins, android { } block, dependencies block. Pass modulePath = absolute path to the module directory (e.g. /path/to/project/app).

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": {
      "modulePath": "<modulePath>"
    },
    "name": "read_gradle"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulePathYesAbsolute path to the Gradle module directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions reading and returning a parsed structure but lacks disclosure of error handling (e.g., file not found), permissions needed, or side effects. Minimal behavioral context beyond the basic action.

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?

The description is a single sentence that efficiently conveys the tool's purpose, output, and parameter usage. No unnecessary words.

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?

Given the lack of output schema, the description partially covers return values (plugins, android block, dependencies) but omits error conditions, structure details, or edge cases. Adequate for a simple read operation but not fully complete.

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?

The description adds value over the schema by specifying that modulePath is an absolute path to the module directory (not the file) and provides an example. Schema coverage is 100%, but the description enriches the parameter meaning.

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?

The description clearly states the verb 'Read' and the resource 'module's build.gradle.kts', and specifies the returned parsed structure (plugins, android block, dependencies). It distinguishes itself from siblings by focusing on Gradle build file parsing.

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?

The description provides an example of the required parameter (modulePath) but does not explicitly state when to use this tool versus sibling tools like get_project_info or read_manifest. No when-not or alternative guidance is given.

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