Skip to main content
Glama

TesterSwap

Start test

start_test

Start testing an app. Install and genuinely use it yourself; upload screenshots in TesterSwap.

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": {
      "app_id": "<app_id>"
    },
    "name": "start_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes

Output Schema

NameRequiredDescriptionDefault
urlYes
stateYes
app_idYes
reasonYes
creditsYes
test_idYes
app_nameYes
deadlineYes
platformYes
next_stepYes
claimed_atYes
approved_atYes
install_urlYes
tester_nameYes
minutes_usedYes
submitted_atYes
use_started_atYes
private_feedbackYes
minimum_use_minutesYes
finish_screenshot_statusYes
install_screenshot_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already indicate this is a non-readonly, non-idempotent action. The description adds a meaningful behavioral obligation beyond that: the agent must install the app, genuinely use it, and upload screenshots in TesterSwap. It does not describe return values or auth requirements, but the added workflow context is substantive.

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 two sentences, front-loads the purpose, and wastes no words. The follow-up sentence adds concrete procedural guidance without padding.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, the description omits prerequisites, selection guidance relative to sibling test lifecycle tools, and any clarification of app_id, leaving meaningful gaps for a workflow-starting tool.

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?

There is only one parameter, app_id, and schema description coverage is 0%. The schema supplies a UUID format and pattern, but the description does not explain that app_id identifies the app to test or add any meaning beyond the implicit phrase 'an app.' This leaves the parameter under-explained.

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 states a specific verb and resource: 'Start testing an app.' This clearly distinguishes it from lifecycle siblings like approve_test, reject_test, and get_test. It does not explicitly name those alternatives, but the core purpose is unambiguous.

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?

The description gives post-call instructions ('Install and genuinely use it yourself; upload screenshots in TesterSwap') but does not explain when to choose start_test over sibling tools like approve_test or get_test. There are no prerequisites or exclusions for selecting this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.