Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

stopTest

Terminate a running test immediately by session ID to halt execution and prevent further resource use.

Instructions

Stop a running test by session ID. This terminates the test execution immediately.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe session ID of the test to stop

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?

With no annotations, the description carries the full burden; it does disclose that termination is immediate, which signals an abrupt, non-graceful stop. It does not say whether partial results survive, what state the test ends in, or how it behaves if the session is already finished.

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?

Two short sentences, purpose front-loaded, with the second sentence adding the immediacy qualifier. Slightly redundant ('Stop' / 'terminates') but no wasted space.

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 one-parameter mutation with no annotations and no output schema, the definition covers what it does and that it is immediate, but omits post-conditions (does the test record persist? can results still be retrieved?). That leaves a meaningful gap for an agent deciding what to do after calling it.

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% for the single sessionId parameter, so the schema already defines it. The description only restates 'by session ID' with no added format, sourcing, or lookup guidance, which is the baseline for full-coverage schemas.

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 ('Stop') and resource ('test') and scopes it to running tests keyed by session ID. That scope helps separate it from deletion/cleanup siblings like deleteTest, though it never names a sibling explicitly.

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?

'Running test' implies the condition for use, but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as a run-cancellation tool for other test types. Usage must be inferred from the verb.

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