Skip to main content
Glama

Check app health

qa_check_health
Read-only

Checks the current app screen for crashes, ANRs, error boundaries, error surfaces, and foreground status, flagging high-severity findings as real bugs during mobile QA.

Instructions

Health check of the current screen: crash, ANR, error boundary, error surface, app still in the foreground. High-severity findings are real bugs. qa_act runs it automatically.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "qa_check_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint false), and the description adds meaningful interpretation guidance beyond that: the specific failure taxonomy it detects and the claim that high-severity findings are real bugs rather than noise. It stops short of describing result shape (pass/fail vs. list of findings) or how findings should be triaged, which matters given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and what is checked, with no filler. The colon list is dense and earns its space; only the trailing automation note feels slightly detached from the rest.

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?

For a read-only single-parameter check with no output schema, the description covers what is detected and how to treat severe findings, but leaves the agent guessing about return shape and next steps after a finding. Adding one clause on returned results or the follow-up sibling would make it 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?

The single required parameter sessionId has 0% schema description coverage, so the description should compensate and does only indirectly via 'current screen' — implying session-scoped behavior but never stating what a session ID is or where it comes from. With one self-descriptive parameter this is a minor rather than crippling gap.

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 ('Health check of the current screen') and enumerates exactly what is detected: crash, ANR, error boundary, error surface, foreground state. That is far more discriminating than the title alone, though it never names how it differs from adjacent checks such as qa_flow_check or qa_mobile_audit.

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?

'qa_act runs it automatically' tells the agent this is normally invoked for it, which implicitly discourages redundant manual calls, but there is no explicit statement of when to call it directly, when not to, or what to use instead after a finding appears.

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