Skip to main content
Glama

rollback

Revert to the previous development phase when a step fails or needs revision, providing a controlled way to correct mistakes during TDD cycles.

Instructions

Rollback to the previous phase.

Args: reason: Reason for rolling back

Returns: New session state after rollback

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
current_phaseYes
cycle_numberYes
goalYes
test_filesYes
implementation_filesYes
run_testsYes
custom_rulesYes
Behavior2/5

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

No annotations exist, and the description only says 'Rollback to the previous phase' without disclosing if the operation is destructive, what happens to the current state, or if there are side effects. The return of 'New session state after rollback' is mentioned but without 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.

Conciseness4/5

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

The description is very concise, using a clear Args/Returns structure. However, it may be too terse, sacrificing useful details for brevity.

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 the tool's role (rollback) and the presence of an output schema, the description should explain the effect of rollback on the session state. It does not, leaving gaps about when and why to rollback compared to siblings like 'history' or 'next_phase'.

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?

The schema has one required parameter 'reason' of type string. The description restates it as 'reason: Reason for rolling back', adding no extra meaning or constraints beyond the schema. Schema description coverage is 0%, but the parameter is simple; still, the description does not enhance understanding.

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 states 'Rollback to the previous phase', which is a specific verb+resource and clearly distinguishes from sibling 'next_phase'. However, it lacks any additional detail about what rollback entails.

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 tool versus alternatives like 'next_phase' or 'end_session'. There is no mention of prerequisites, when-not to use, or examples.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tinmancoding/tdd-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server