Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadMaestroCompanionApp

Upload a companion app (.apk/.aab/.ipa) to install alongside the Maestro app under test, returning a tb:// URL for runMaestroTest's otherApps parameter.

Instructions

Upload a companion app (.apk/.aab/.ipa) that should be installed alongside the app under test in a Maestro run. Returns a tb:// app URL to pass in runMaestroTest's otherApps parameter (max 4 per run).

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": {
      "localFilePath": "<localFilePath>"
    },
    "name": "uploadMaestroCompanionApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
localFilePathYesLocal path to the companion .apk, .aab, .ipa or .zip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does disclose the accepted formats, the return value shape (tb:// app URL), and the per-run cap of 4. It does not say whether re-uploading the same file overwrites or duplicates, what size/time limits apply, or what happens on failure, which are material for an upload operation with zero annotation coverage.

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, zero filler, with the purpose front-loaded and the practical constraint (max 4) and return contract packed into the second. Every clause earns its place.

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

Completeness4/5

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

For a single-parameter upload with no output schema, the description covers purpose, accepted formats, return value, and the 4-per-run limit, so an agent can call it correctly. Missing are lifecycle details such as overwrite/idempotency behavior and any size limits, which keep it short of fully complete.

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?

There is a single parameter at 100% schema description coverage, so the schema already documents localFilePath. The description only restates the file types (and actually omits .zip, which the schema lists), adding no new meaning such as whether relative paths are accepted. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Upload a companion app (.apk/.aab/.ipa)') and pins down the scope: the app is installed alongside the app under test in a Maestro run, which implicitly distinguishes it from uploading the app under test itself (uploadMaestroApp). An agent can tell what it does and where it fits without opening the schema.

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

Usage Guidelines4/5

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

It gives clear downstream usage: the returned tb:// app URL goes into runMaestroTest's otherApps parameter, and it states the max of 4 per run. There is no explicit when-not guidance (e.g., only for Maestro runs, not App Automate), but the context is concrete enough for correct selection.

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