Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

setupTestingBot

Detects a project's testing framework and returns ready-to-paste TestingBot configuration, install command, and required environment variables without modifying files.

Instructions

Detect the testing framework in a project and return the ready-to-paste TestingBot configuration snippet, install command, and env-var requirements. Read-only — never modifies files; the agent or user applies the snippet.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "setupTestingBot"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectRootYesAbsolute path to the project root to inspect.
frameworkOverrideNoForce a specific framework instead of using auto-detection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does the most important part: "Read-only — never modifies files; the agent or user applies the snippet." That tells the agent this returns text rather than mutating the project, which is exactly the fact a naive caller would get wrong. Gaps remain: nothing is said about what happens when no framework is detected, or any auth/permission requirements.

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 sentences, zero filler. The behavioral caveat (read-only, agent applies the snippet) is placed last where it caps the capability claim, and the return contents are listed up front so the agent knows the payoff immediately.

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-parameter tool with no output schema, the description is nearly sufficient: it names the inputs implicitly, the outputs explicitly, and the non-mutating contract. The only real omission is the failure mode when the framework cannot be detected, which an agent would need in order to plan a fallback.

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 projectRoot ("absolute path to the project root to inspect") and the frameworkOverride enum are already fully documented. The description mentions "in a project" but adds no syntax, format, or override behavior beyond what the schema states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Detect the testing framework in a project") and then enumerates the exact artifacts returned: a TestingBot config snippet, install command, and env-var requirements. That is far more precise than anything in the sibling set (runs, builds, tunnels, devices), so an agent can distinguish it without opening the schema.

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 conveys the operating context clearly: this is the setup-time tool that produces configuration the agent or user then applies. It does not name alternatives or state exclusions, but no sibling overlaps in function, so the missing routing guidance is minor.

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