Skip to main content
Glama
Sign In
TDD-MCP

TDD-MCP

by tinmancoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_session

Update an active TDD session by providing new goal, test files, implementation files, test commands, or custom rules.

Instructions

Update an existing active session.

Args: goal: Updated session objective (optional) test_files: Updated test files (optional) implementation_files: Updated implementation files (optional) run_tests: Updated test commands (optional) custom_rules: Updated custom rules (optional)

Returns: True if update was successful

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

Input Schema

NameRequiredDescriptionDefault
goalNo
test_filesNo
implementation_filesNo
run_testsNo
custom_rulesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.6/5.0
Behavior2/5

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

The description mentions it returns True on success but lacks details on error behavior, idempotency, or what happens if the session is not active. With no annotations, more behavioral detail is needed.

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

Conciseness3/5

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

The description is fairly concise but repeats parameter names that are already in the schema. The Args/Returns format is clean.

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

Completeness2/5

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

Given 5 optional parameters at 0% schema coverage and no annotations, the description is insufficient. It does not cover validation, side-effects, or relationship to other session management tools.

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

Parameters2/5

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

Parameters are listed with their names and optionality, but no additional meaning beyond the schema (which has 0% coverage). For example, 'goal' is not explained beyond 'Updated session objective'.

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 the tool updates an existing active session and lists the updatable fields. However, it does not differentiate from sibling tools like end_session or pause_session.

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 on when to use this tool versus alternatives like start_session or pause_session. No prerequisites or contextual advice.

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