Repo Test Architect

Overview Schema Source Related Servers Discussions Admin

Detect Projects

detect_projects

Read-onlyIdempotent

Discover project roots, support status, and matching adapters from local repository markers before specialized workflows, without auditing source targets or writing files.

Instructions

Discover project roots, support status, and matching adapters without auditing source targets. Use this when project boundaries are needed before a specialized workflow; use analyze_repository for a complete review. Reads local repository markers and returns project-detection/v1 without executing tests or writing files.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`repoRoot`	Yes	Readable repository directory whose project markers should be inspected.
`excludeProjectRoots`	No	Optional exact project roots or subtree patterns such as examples/** to exclude before returning detected projects.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`root`	Yes
`summary`	Yes
`projects`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Oct 2, 2026

changedInput schema / properties / repoRoot / description

Previous value: -"Repository root path."New value: +"Readable repository directory whose project markers should be inspected."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$id": "project-detection-v1.schema.json",
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "projects": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "absoluteRoot": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "adapterIds": {
+            "items": {
+              "minLength": 1,
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "adapterMatches": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "adapterId": {
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "matchedEcosystems": {
+                  "items": {
+                    "minLength": 1,
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "matchedLanguages": {
+                  "items": {
+                    "minLength": 1,
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "maturity": {
+                  "enum": [
+                    "supported",
+                    "experimental",
+                    "planned"
+                  ]
+                }
+              },
+              "required": [
+                "adapterId",
+                "maturity",
+                "matchedEcosystems",
+                "matchedLanguages"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "ecosystems": {
+            "items": {
+              "minLength": 1,
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "languages": {
+            "items": {
+              "minLength": 1,
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "markerFiles": {
+            "items": {
+              "minLength": 1,
+              "type": "string"
+            },
+            "minItems": 1,
+            "type": "array"
+          },
+          "root": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "supportStatusReason": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "supported": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "id",
+          "root",
+          "absoluteRoot",
+          "ecosystems",
+          "languages",
+          "markerFiles",
+          "adapterIds",
+          "adapterMatches",
+          "supported",
+          "supportStatusReason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "root": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "schemaVersion": {
+      "const": "project-detection/v1"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "projectCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "supportedProjectCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "unsupportedProjectCount": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "projectCount",
+        "supportedProjectCount",
+        "unsupportedProjectCount"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "root",
+    "projects",
+    "summary"
+  ],
+  "title": "Project Detection Artifact",
+  "type": "object"
+}

First observedv0.1.0Aug 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: it reads local repository markers, returns a versioned shape (project-detection/v1), and explicitly does not execute tests or write files. It stops short of describing exclusion semantics or output granularity, so not a 5.

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?

Three sentences, front-loaded with the core capability, then the usage routing, then behavioral limits. No filler and every clause carries information.

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?

An output schema exists, so return values need not be explained, and the description still names the result shape. Combined with full schema coverage and rich annotations, the only minor gap is exclusion-pattern behavior, which is left to the parameter schema.

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 both repoRoot and excludeProjectRoots are already documented with examples (e.g. 'examples/**'). The description adds nothing beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource set ('Discover project roots, support status, and matching adapters') and immediately scopes it against auditing ('without auditing source targets'). An agent can distinguish this detection tool from analyze_repository or audit_projects without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to reach for it ('when project boundaries are needed before a specialized workflow') and names the alternative for a different need ('use analyze_repository for a complete review'). The routing condition and the alternative are both explicit.

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