Skip to main content
Glama
Sign In
Claude Code Starter Kit MCP

Claude Code Starter Kit MCP

by dachivadachkoria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agent_test_engineer

Generates comprehensive test suites for your codebase. Accepts optional file paths or flags like --changed to focus on specific changes.

Instructions

Specialized agent for comprehensive test generation

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

Input Schema

NameRequiredDescriptionDefault
argumentsNoOptional arguments for the tool (e.g. a file path or flags like --changed, --dry-run).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, permissions, or behavior when called. The description only states a vague purpose without actionable behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) but lacks substance. It is concise but not informative, failing to earn its place with meaningful content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is an agent with many siblings and no output schema, the description is severely incomplete. It does not explain what 'comprehensive test generation' entails, how arguments affect behavior, or what the agent returns.

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 100% for the single parameter, and the description adds no extra meaning beyond the schema's own description. The baseline score of 3 is appropriate as the schema already handles parameter documentation.

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

Purpose3/5

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

The description indicates the tool is for test generation, which is clear but vague. It does not specify the type of tests (unit, integration, etc.) or how it differs from sibling tools like command_test or command_test_coverage.

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?

No guidance is provided on when to use this agent versus alternatives. With many sibling agents and commands, the lack of usage context makes it difficult for an AI agent to select the correct tool.

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

Deploy Server

Other Tools