MCP Server By TestMu AI

Check App Processing Status (Real Device)

checkAppProcessingStatus

Idempotent

Check whether an uploaded app has been processed and is ready for features like image injection, network logs, and screenshot unblock on real devices. The TestMu AI API has no read-only status call: this one starts or refreshes the processing for the requested features, so the app's last-updated time changes. An app id that is not among your uploaded apps returns an error.

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": {
      "appId": "<appId>"
    },
    "name": "checkAppProcessingStatus"
  }
}

Input Schema

Name	Required	Description
`appId`	Yes	The app ID to check
`networkLogsEnabled`	No	Check network logs support
`imageInjectionEnabled`	No	Check image injection support
`screenshotUnblockEnabled`	No	Check screenshot unblock support

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it explains that despite the 'check' name, the call starts or refreshes processing, changes the app's last-updated time, and returns an error for app IDs not owned by the caller. This aligns with readOnlyHint=false and destructiveHint=false and meaningfully warns the agent about the side effect.

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 three tightly focused sentences: purpose first, critical side effect second, and error behavior third. All content is front-loaded and each sentence contributes information the agent needs.

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?

The description covers the important hidden side effect and error condition, which are essential for correct invocation. However, because there is no output schema, it would benefit from describing the return shape, such as whether it returns per-feature readiness booleans or a status object.

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%, so the four parameters are already documented in the schema. The description names the feature types in prose but adds no syntax, defaults, or other parameter-level meaning beyond what the schema provides.

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 a specific verb and resource: checking whether an uploaded app has been processed and is ready for real-device features. It does not explicitly name or differentiate this tool from sibling tools, but the purpose is otherwise unambiguous.

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 implies the tool is used after uploading an app to verify processing readiness, but it does not explicitly state when to use it versus alternatives such as listUploadedApps or upload_app. The warning about not being a read-only status call is useful but is more behavioral context than usage routing.

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

All MCP Server By TestMu AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?