Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

runAccessibilityTest

Start a scheduled accessibility scan immediately, then poll accessibility runs to track the new test result.

Instructions

Start a scan of a scheduled accessibility test now (like Run now in the dashboard). Poll getAccessibilityRuns for the new 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": {
      "testId": "<testId>"
    },
    "name": "runAccessibilityTest"
  }
}

Input Schema

NameRequiredDescriptionDefault
testIdYesID of the accessibility test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose key behavior: the scan starts asynchronously and results must be fetched from getAccessibilityRuns. However, it says nothing about permissions, what happens if a run is already in progress, rate limits, or whether the call returns anything useful itself.

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 short sentences, front-loaded with the action and followed by the required follow-up step. Every clause earns its place and there is no redundant restatement of the name.

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 one-parameter trigger tool with no output schema, the definition covers the action and the async follow-up, which is the critical information. The only gap is what the call itself returns, which leaves some ambiguity about how the agent locates the new run.

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 testId is fully documented in the schema as 'ID of the accessibility test.' The description adds no further meaning about the parameter, so the baseline of 3 applies.

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 definition uses a concrete verb and resource, 'Start a scan of a scheduled accessibility test now,' and distinguishes this tool from other run tools via the phrase 'scheduled accessibility test.' It does not explicitly disambiguate from runMaestroTest or runAppAutomateTest, but the domain is clear.

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 clearly states the use case ('like Run now in the dashboard') and tells the agent what to do next: 'Poll getAccessibilityRuns for the new run.' It never states when not to use it or what alternatives exist for different test types, so a 4 is appropriate rather than a 5.

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