TDD-MCP

by tinmancoding

Overview Schema Source Related Servers Discussions Admin

Python

Local

resume_session

Resume a saved TDD session by providing its unique session ID to restore the current state and continue development.

Instructions

Resume an existing session by session ID.

Args: session_id: Unique identifier for the session to resume

Returns: Current state of the resumed 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": {
      "session_id": "<session_id>"
    },
    "name": "resume_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes

Output Schema

Name	Required	Description	Default
`session_id`	Yes
`current_phase`	Yes
`cycle_number`	Yes
`goal`	Yes
`test_files`	Yes
`implementation_files`	Yes
`run_tests`	Yes
`custom_rules`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 30, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. It only mentions resuming and returning state, but omits prerequisites (session must exist and be paused), side effects, or error conditions.

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 sentences, front-loaded with action and result, no wasted words.

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?

For a simple one-parameter tool with output schema mentioned, the description covers the core functionality but could mention that the session must be in a resumable state for clarity.

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?

The parameter session_id is described as 'Unique identifier for the session to resume', adding value beyond the schema's type-only definition. Schema coverage is 0%, so description compensates well.

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 clearly states the tool resumes an existing session by ID, and this purpose is distinct from siblings like start_session, pause_session, end_session which handle different session lifecycle actions.

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?

Usage is implied (resume when you have a session ID), but no explicit guidance on when to use versus alternatives like start_session for new sessions or pause_session before resume.

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

Deploy Server