Skip to main content
Glama
Repo Test Architect

Repo Test Architect

Analyze Project Test Placement

analyze_project_test_placement
Read-onlyIdempotent

Derive advisory test-placement findings for audited projects from an existing project-audits artifact or a fresh repository audit, without executing tests or changing files.

Instructions

Derive advisory test-placement findings across audited projects while preserving project identity, from a project-audits/v1 artifact or, with repoRoot, from a fresh audit. Use analyze_test_placement for one project. Does not execute tests or create, move, or modify files.

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

Input Schema

NameRequiredDescriptionDefault
goTargetNo
repoRootNoRepository root to audit instead of passing projectAudits.
changedPathsNoOptional repository-relative source paths to limit target selection.
projectAuditsNoA project-audits/v1 artifact; or pass repoRoot instead.
excludeProjectRootsNoOptional project roots or subtree patterns such as examples/** to exclude before auditing.

Output Schema

NameRequiredDescriptionDefault
findingsYes
auditCoverageNo
schemaVersionYes
failedProjectsNo
failedProjectCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.0
    • addedInput schema / properties / changedPaths
      Added value: +{
      +  "description": "Optional repository-relative source paths to limit target selection.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / excludeProjectRoots
      Added value: +{
      +  "description": "Optional project roots or subtree patterns such as examples/** to exclude before auditing.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / goTarget
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "goarch": {
      +      "description": "Explicit GOARCH for bounded Go build-constraint evaluation.",
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "goos": {
      +      "description": "Explicit GOOS for bounded Go build-constraint evaluation.",
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "tags": {
      +      "description": "Optional custom Go build tags passed to the target-aware verification command.",
      +      "items": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "goos",
      +    "goarch"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / projectAudits / description
      Previous value: -"The project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path."New value: +"A project-audits/v1 artifact; or pass repoRoot instead."
    • addedInput schema / properties / repoRoot
      Added value: +{
      +  "description": "Repository root to audit instead of passing projectAudits.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "projectAudits"
      -]New value: +[]
  2. Changed8 schema fields changedv1.1.0
    • removedOutput schema / $id
      Removed value: -"test-placement-findings-v1.schema.json"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / description
      Added value: +"Top-level shape of this artifact. The complete contract is schemas/test-placement-findings-v1.schema.json in the published package."
    • addedOutput schema / properties / auditCoverage
      Added value: +{
      +  "enum": [
      +    "partial",
      +    "none"
      +  ]
      +}
    • addedOutput schema / properties / failedProjectCount
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / failedProjects
      Added value: +{
      +  "type": "array"
      +}
    • removedOutput schema / properties / findings / items
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "action": {
      -      "enum": [
      -        "move",
      -        "split",
      -        "keep"
      -      ]
      -    },
      -    "currentOwner": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "evidence": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "minItems": 1,
      -      "type": "array"
      -    },
      -    "id": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "reason": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "suggestedOwner": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "testFile": {
      -      "minLength": 1,
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "id",
      -    "testFile",
      -    "currentOwner",
      -    "suggestedOwner",
      -    "action",
      -    "reason",
      -    "evidence"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / title
      Removed value: -"Test Placement Findings Artifact"
  3. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / projectAudits / description
      Previous value: -"A project-audits/v1 artifact."New value: +"The project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$id": "test-placement-findings-v1.schema.json",
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "findings": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "action": {
      +            "enum": [
      +              "move",
      +              "split",
      +              "keep"
      +            ]
      +          },
      +          "currentOwner": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "evidence": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "minItems": 1,
      +            "type": "array"
      +          },
      +          "id": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "reason": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "suggestedOwner": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "testFile": {
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "testFile",
      +          "currentOwner",
      +          "suggestedOwner",
      +          "action",
      +          "reason",
      +          "evidence"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "schemaVersion": {
      +      "const": "test-placement-findings/v1"
      +    }
      +  },
      +  "required": [
      +    "schemaVersion",
      +    "findings"
      +  ],
      +  "title": "Test Placement Findings Artifact",
      +  "type": "object"
      +}
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value beyond that by stating 'Does not execute tests' — a runtime behavior the annotations do not express — and by promising 'preserving project identity.' It does not mention cost or latency of a fresh audit versus reading an artifact, which would have been the natural remaining disclosure.

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 sentences, front-loaded with the purpose and the input modes, then the sibling routing and the negative guarantees. Nothing is redundant, though the phrase 'while preserving project identity' is vague enough to be near-noise without further explanation.

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?

With an output schema present and rich annotations, the description does not need to explain return values, and it covers the key facts an agent needs: input modes, single-project alternative, and the absence of test execution or file writes. The remaining gap is that nested goTarget and the changedPaths/excludeProjectRoots filters are never framed, which matters given the nested-object complexity.

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 80%, so the baseline is 3. The description reinforces the mutually exclusive relationship between projectAudits and repoRoot, which is useful but already stated in the schema ('A project-audits/v1 artifact; or pass repoRoot instead'). It says nothing about goTarget, changedPaths, or excludeProjectRoots, so it adds little semantics beyond the structured fields.

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 states a specific verb and resource ('Derive advisory test-placement findings across audited projects') and explicitly bounds the scope versus the single-project sibling: 'Use analyze_test_placement for one project.' Combined with the two named input sources ('project-audits/v1 artifact' or 'repoRoot ... fresh audit'), an agent can identify the tool and distinguish it from the nearest alternative without opening either 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 gives clear routing guidance for the single-project case by naming analyze_test_placement, and it explains the two input modes (artifact vs. repoRoot-driven fresh audit). What it leaves implicit is which mode to prefer when both are available, and it offers no exclusion for the broader audit/repository tools in the sibling list.

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