Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

summarize_done_phases

Automatically summarizes completed workflow phases, saves the summary to a specified library, and deletes the original phases to streamline the project plan.

Instructions

Generate an AI summary of all done phases in a workflow's project plan, save it as a context file in the specified library, then delete the source phases. Updates the plan's last_summarized_at timestamp.

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": {
      "workflowId": "<workflowId>",
      "libraryId": "<libraryId>",
      "summaryTitle": "<summaryTitle>"
    },
    "name": "summarize_done_phases"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryIdYesLibrary ID to save the summary file into.
workflowIdYesWorkflow ID
workspaceIdNoWorkspace ID. Defaults to your configured workspace.
summaryTitleYesTitle for the summary file, e.g. "Auth Rewrite — June 2026".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description explicitly states the destructive action ('delete the source phases') and the creation of a context file. Given no annotations, this disclosure is critical for safe invocation, though it could mention permanence or recovery options.

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 with no fluff, directly stating the purpose, the sequence of actions, and the side effect. It is front-loaded and efficient.

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?

The description covers the main workflow: summarize, save, delete, update timestamp. For a multi-step destructive tool with no output schema, it is fairly complete, though it lacks mention of prerequisites or reversal steps.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds a real-world example for summaryTitle but does not significantly enhance understanding beyond what the schema already provides for the other parameters.

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 generates an AI summary of done phases, saves it to a library, deletes the source phases, and updates a timestamp. This specific combination of actions differentiates it from sibling tools like delete_done_phases, which only deletes without summarizing.

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 about when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or compare with similar tools like delete_done_phases or add_phase.

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