Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAccessibilityTests

List scheduled accessibility tests with each target URL and latest result to review scan status and outcomes.

Instructions

List the account's scheduled accessibility tests (each scans one URL) with their latest result.

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": "getAccessibilityTests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tests (max 100).
offsetNoSkip this many tests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key output shape (each scheduled test plus its latest result) and "List" signals a read-only operation, but it says nothing about pagination behavior, ordering, or what happens when a test has never run.

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?

A single front-loaded sentence with zero filler; the parenthetical clarification earns its place by pinning down the unit of the resource.

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 two-optional-parameter read-only list tool with a fully documented schema, this is close to sufficient: it identifies the resource and the included latest-result payload. Only pagination/ordering behavior and the never-run case are left unstated.

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 both limit and offset carry their own descriptions (max 100, skip count, defaults). The description adds no meaning beyond that, so the baseline 3 is correct.

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 ("List the account's scheduled accessibility tests") and adds the disambiguating detail that each test scans one URL and comes with its latest result. That distinguishes it implicitly from getAccessibilityRuns and getAccessibilityFindings, though no sibling is named explicitly.

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?

There is no explicit when-to-use guidance or named alternative. An agent can infer this is for enumerating scheduled test configurations rather than run history or findings, but that inference comes from the noun phrase, not from any stated routing rule.

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