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

Claude Code Starter Kit MCP

by dachivadachkoria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

command_test

Automatically generate comprehensive unit tests for a specific file or all changed files using optional flags. Preview test output with --dry-run.

Instructions

Generate comprehensive unit tests for files. Use /test or /test --changed

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

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

B3.3/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral details such as whether the tool modifies files, requires permissions, or has side effects.

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 concise with two sentences, front-loaded with the purpose, and contains no unnecessary words.

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?

Given the lack of output schema and annotations, the description adequately covers usage but misses details on behavioral outcomes and error conditions.

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?

The single parameter 'arguments' is well-described in the schema (100% coverage). The description adds usage examples but does not provide additional semantic value beyond the schema.

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 clearly states it generates unit tests for files and provides a usage example. However, it does not differentiate from sibling tools like 'command_test_coverage' or 'agent_test_engineer'.

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 description includes usage examples ('Use /test <file> or /test --changed') but lacks explicit guidance on when not to use this tool or how it compares to alternatives.

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