Skip to main content
Glama
Sign In
Swipium

Swipium

by GeroPalombo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

QA environment doctor

qa_doctor
Read-only

Diagnose local QA toolchain issues and stale-client symptoms across Node, Android SDK/emulator, Xcode/simctl, and WDA. Run it first when setup fails to pinpoint the cause.

Instructions

Diagnose the local QA toolchain (Node, Android SDK/emulator, Xcode/simctl, WDA) and stale-client symptoms; run it first when setup fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qa_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNoTailor setup hints to this MCP client.
platformNoDefault both on macOS (ready if either is), else android.
expectedVersionNoVersion you expect; a mismatch means a stale client.
expectedToolCountNoTool count you expect; a mismatch means a stale client.
expectedSchemaHashNoSurface hash you expect; a mismatch means a stale client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds that it detects "stale-client symptoms" by comparing expected versions/counts/hashes, which is useful context beyond annotations, but it says nothing about runtime, output shape, or failure semantics.

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?

A single tight sentence with the actionable instruction ("run it first") placed at the end where it reads as the next step. No wasted wording, though the ordering could front-load the trigger.

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 read-only diagnostic with fully documented optional parameters and no output schema, this covers what it inspects and when to invoke it. Minor gap: no hint that it is the entry point of an ordered recovery flow versus qa_check_health.

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 coverage is 100% and each parameter already carries a description tying mismatches to a stale client, so the schema does the heavy lifting. The description only alludes to "stale-client symptoms" without adding parameter-level meaning such as how expected values are compared or what client/platform defaults apply.

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?

Specific verb ("Diagnose") plus a concrete resource list (Node, Android SDK/emulator, Xcode/simctl, WDA) and an added scope of stale-client symptoms. It is clear what the tool does, though it does not differentiate itself from near-neighbors such as qa_check_health or qa_device_info.

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?

Explicit trigger: "run it first when setup fails" gives a clear when-to-use rule. It stops short of saying when not to use it or naming the sibling diagnostic tools to prefer in other situations.

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

Deploy Server

Other Tools