Skip to main content
Glama
Sign In
TDD-MCP

TDD-MCP

by tinmancoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_session

Initialize a TDD session with a goal, test and implementation files, test commands, and custom rules.

Instructions

Start a new TDD session.

Args: goal: High-level session objective and definition of done test_files: Files where agent can write tests (explicit paths) implementation_files: Files where agent can write implementation run_tests: Commands/instructions for running test suite custom_rules: Additional rules appended to global TDD rules

Returns: Session ID of the created session

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": {
      "goal": "<goal>",
      "test_files": "<test_files>",
      "implementation_files": "<implementation_files>",
      "run_tests": "<run_tests>"
    },
    "name": "start_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
test_filesYes
implementation_filesYes
run_testsYes
custom_rulesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4/5.0
Behavior3/5

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

Describes starting a session and returning a session ID, but lacks details on side effects like whether it ends existing sessions or requires a clean state. No annotations provided to compensate.

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?

Docstring format with clear Args and Returns sections. First sentence states purpose immediately. No redundant 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?

Covers all necessary parameters and return value for starting a session. Could mention potential conflicts (e.g., only one active session), but overall sufficient given the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the Arg section adds meaningful descriptions for each parameter, explaining their roles. However, it lacks details on format constraints or expected content.

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?

Clearly states 'Start a new TDD session', giving a specific verb and resource. Differentiates from sibling tools like end_session, pause_session, and resume_session.

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 implies this tool is used to initiate a session, but it doesn't explicitly state when to use it or when not to, nor does it mention alternatives. Usage is clear by context but not explicit.

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