Skip to main content
Glama

test

Run tests for Android projects to verify functionality and identify issues. Specify the project folder path to execute test suites directly within your development environment.

Instructions

Run test for the Android project in the folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderYesThe full path of the current folder that the Android project sits

Implementation Reference

  • Dispatch logic in the call_tool handler that sets the command to execute test.sh for the 'test' tool.
    command = [""]
    if name == "build":
        command = [os.path.join(script_dir, "build.sh"), args.folder]
    elif name == "test":
        command = [os.path.join(script_dir, "test.sh"), args.folder]
    else:
        command = [os.path.join(script_dir, "instrumentedTest.sh"), args.folder]
  • Subprocess execution and result processing logic shared by all tools including 'test', extracting error lines or success message.
    result = subprocess.run(command, stdout=subprocess.PIPE, stderr=subprocess.PIPE, check=False)
    stdout_lines = result.stdout.decode("utf-8").splitlines()
    stderr_lines = result.stderr.decode("utf-8").splitlines()
    all_lines = stdout_lines + stderr_lines
    
    
    error_lines = [line for line in all_lines if "failure: " in line.lower() or "e: " in line.lower() or " failed" in line.lower()]
    error_message = "\n".join(error_lines)
    if not error_message:
        error_message = "Successful"
    return [
        TextContent(type="text", text=f"{error_message}")
        ]
  • Pydantic BaseModel defining the input schema for the 'test' tool: a folder path.
    class Folder(BaseModel):
        """Parameters"""
        folder: Annotated[str, Field(description="The full path of the current folder that the Android project sits")]
  • Registration of the 'test' tool in the list_tools() function.
    Tool(
        name="test",
        description="Run test for the Android project in the folder",
        inputSchema=Folder.model_json_schema(),
    ),
  • Helper to compute the script directory for locating shell scripts like test.sh.
    script_dir = os.path.dirname(os.path.abspath(__file__))
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions running tests but doesn't disclose execution details (e.g., test environment, output format, side effects, or error handling). For a tool with zero annotation coverage, this is inadequate.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it easy to parse quickly.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It lacks details on test execution behavior, output expectations, error conditions, and differentiation from sibling tools, leaving significant gaps for an agent to understand proper usage.

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%, with the single parameter 'folder' well-documented in the schema. The description adds no additional parameter semantics beyond implying the folder contains an Android project, which is already inferred from the schema's description. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Run test') and target ('for the Android project in the folder'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'build' or 'instrumentedTest', which likely have overlapping testing-related functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'instrumentedTest'. The description implies it runs tests for Android projects, but doesn't specify test types, prerequisites, or exclusions, leaving usage context unclear.

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/ShenghaiWang/androidbuild'

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