Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

listTestFiles

Locate test files in a project directory by scanning it and returning paths for the detected framework. Read-only, with configurable depth and result limits.

Instructions

Scan a project directory and return test files for the detected framework. Read-only — never modifies files.

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

Input Schema

NameRequiredDescriptionDefault
maxDepthNoMax directory depth to walk (default 8).
maxResultsNoCap on returned file paths (default 200, max 2000).
projectRootYesAbsolute path to the project root to scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/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 burden; it does disclose the important trait that the operation is read-only and never modifies files. However, it omits other behavior an agent would want: what happens when no framework is detected, whether ignored directories (node_modules, .git) are skipped, and whether results are ordered. Useful but incomplete.

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 core action and followed by the safety trait. No redundant restatement of the schema, no filler; every sentence earns its place.

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?

With no output schema, the description should convey the return shape, and it only implies a flat list of paths via 'return test files'. It also leaves 'detected framework' unexplained and says nothing about empty results or scanning failures. Adequate for a simple discovery call, but with clear gaps.

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%: projectRoot, maxDepth and maxResults are each documented with defaults and bounds in the schema, so the baseline is 3. The description adds no parameter meaning beyond the schema — it does not explain, for example, how depth affects cost or why a caller would lower maxResults.

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 concrete verb+resource: scans a project directory and returns test files, plus the qualifier that the framework is auto-detected. That is clearly distinguishable from siblings like listMaestroProjects (projects) or getTestDetails (a single test). It does not explicitly name an alternative, keeping it at 4 rather than 5.

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 when-to-use guidance: nothing says whether this is the entry point before runMaestroTest or how it differs from getTestDetails or listMaestroProjects. An agent must infer that it is a discovery tool from the name alone.

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