Skip to main content
Glama
Sign In
total-agent-memory

total-agent-memory

by vbcherepanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

phase_transition

Advance a task to a specified new phase, optionally attaching notes and artifacts to document the transition.

Instructions

v8.0: advance a task to the next phase.

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": {
      "task_id": "<task_id>",
      "new_phase": "<new_phase>"
    },
    "name": "phase_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
task_idYes
artifactsNo
new_phaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The word 'advance' implies a state change, which aligns with readOnlyHint=false, but no additional behavioral traits are disclosed. It does not mention side effects, return values, or other outcomes beyond the transition itself.

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 a single, succinct sentence with no redundancy. It front-loads the verb and object, making the core operation immediately clear.

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

Completeness1/5

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

The description is extremely sparse. It omits details about phase definitions, the role of notes and artifacts, whether the transition is reversible, and what the output or result might be. Given the complexity of the sibling toolset, this is insufficient.

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

Parameters1/5

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

None of the parameters (task_id, new_phase, notes, artifacts) are described. Their names hint at their purpose, but there is no explicit semantic detail about expected values, formats, or how they affect the transition.

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 action ('advance') and the object ('a task to the next phase'), but lacks context about what a 'phase' is or how this action differs from other task-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 task_create or task_phases_list. The description gives no situational context or prerequisites.

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