Skip to main content
Glama
Sign In
android-build-agent

android-build-agent

by Tommyface
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

android_get_build_result

Retrieve a project's last build result for a given profile, including APK list and log tail, without starting a new build.

Instructions

读取某个项目最近一次构建结果（含 APK 清单与日志尾部），不触发构建。

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": {
      "profile": "<profile>"
    },
    "name": "android_get_build_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose the read-only nature and that output includes the APK manifest and log tail. It says nothing about behavior when no prior build exists, permissions/authentication, or whether log output is truncated.

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?

A single compact sentence that front-loads the action, then the returned content, then the side-effect disclaimer. Nothing is redundant.

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?

A simple one-parameter read tool with no output schema, so the description needn't explain return structure in depth. However, the sole required parameter is undefined and retry/failure behavior is unaddressed, leaving real gaps for correct invocation.

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

Parameters2/5

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

The single required parameter 'profile' has 0% schema description coverage and is never mentioned in the description. The agent cannot tell whether 'profile' is a build profile, a project identifier, or a value obtained from android_list_profiles.

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 and resource ('read the most recent build result of a project') and adds what the result contains (APK manifest, log tail). The clause 'does not trigger a build' effectively separates it from android_build, though the sibling is not named.

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 gives a clear when-not ('does not trigger a build'), implying you must call android_build first to produce a result. It does not state when to prefer this over other inspection routes or what to do if no build exists.

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