Skip to main content
Glama
Repo Test Architect

Repo Test Architect

Generate Selected Test (Deferred)

generate_selected_test
Read-onlyIdempotent

Returns a structured deferred result for a selected test plan item, marking it for future generation while native test generation is disabled.

Instructions

Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled.

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": {
      "planItemId": "<planItemId>"
    },
    "name": "generate_selected_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
planItemIdYesStable plan item id selected for future generation.

Output Schema

NameRequiredDescriptionDefault
reasonYes
statusYes
nextStepsYes
planItemIdYes
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.0
    • removedOutput schema / $id
      Removed value: -"https://repo-test-architect.local/schemas/generation-deferred-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/generation-deferred-v1.schema.json in the published package."
    • removedOutput schema / properties / nextSteps / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / title
      Removed value: -"Repo Test Architect Generation Deferred"
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$id": "https://repo-test-architect.local/schemas/generation-deferred-v1.schema.json",
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "nextSteps": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "planItemId": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "schemaVersion": {
      +      "const": "generation-deferred/v1"
      +    },
      +    "status": {
      +      "const": "deferred"
      +    }
      +  },
      +  "required": [
      +    "schemaVersion",
      +    "planItemId",
      +    "status",
      +    "reason",
      +    "nextSteps"
      +  ],
      +  "title": "Repo Test Architect Generation Deferred",
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context by explicitly stating that no code is generated or written despite the tool name, which prevents misuse; it does not explain the deferred result's structure, but an output schema exists.

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?

The description is two short sentences with no wasted words. The most important constraint comes first and the no-generation caveat is front-loaded immediately after.

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, complete parameter coverage, and annotations covering safety, the description provides enough context to prevent an agent from expecting actual generation. It does not explain what happens if native generation is enabled, but the tool title and description strongly imply a deferred-only state.

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% and the single parameter planItemId is already documented as a stable plan item id selected for future generation. The description does not add further meaning beyond the schema, so the baseline 3 is appropriate.

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?

The description states a specific behavior: it returns a structured deferred result and explicitly does not generate or write test code while native generation is disabled. This clarifies the tool's apparent purpose despite the name 'generate_selected_test', though it does not directly differentiate itself from sibling generation tools beyond the disabled-mode caveat.

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?

The phrase 'while native generation remains disabled' implies the tool is intended for a deferred/no-op scenario, but it does not explicitly say when to use this instead of generate_test_plan or other generation siblings. Usage is implied rather than directed.

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