Skip to main content
Glama

dumpPlan

Export complete plan data as a dictionary for backup or state restoration using loadPlan tool in MCPlanManager's task management system.

Instructions

导出当前完整的计划数据为一个字典对象。 这个导出的对象可以被 loadPlan 工具用来恢复状态。

Returns: ToolResponse[dict]: 包含当前完整计划数据的响应对象。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for dumpPlan, registered via @mcp.tool() decorator. Delegates to PlanManager.dumpPlan().
    @mcp.tool()
    def dumpPlan() -> ToolResponse[dict]:
        """
        导出当前完整的计划数据为一个字典对象。
        这个导出的对象可以被 loadPlan 工具用来恢复状态。
    
        Returns:
            ToolResponse[dict]: 包含当前完整计划数据的响应对象。
        """
        return plan_manager.dumpPlan()
  • Core implementation of dumpPlan in PlanManager class. Returns a deep copy of the entire plan data wrapped in a ToolResponse-like dict.
    def dumpPlan(self) -> Dict:
        """导出完整的计划数据为一个字典对象。"""
        return {
            "success": True,
            "data": deepcopy(self.plan_data),
            "message": "Plan dumped successfully."
        }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the core functionality (exporting complete plan data as a dictionary) and mentions the output can be used by loadPlan for state restoration, which adds useful context. However, it doesn't disclose potential side effects, performance characteristics, or detailed behavioral traits beyond the basic operation.

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 perfectly concise with two focused sentences: the first explains what the tool does and its relationship to loadPlan, the second describes the return value. Every sentence earns its place, and the information is front-loaded with the core purpose stated immediately.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description provides adequate context by explaining the export functionality, the dictionary format output, and the relationship with loadPlan. For a simple data export tool, this is reasonably complete, though it could potentially mention performance considerations for large plans.

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 tool has 0 parameters with 100% schema description coverage, so the baseline would be 4 even without parameter information in the description. The description appropriately doesn't discuss parameters since none exist, and instead focuses on the tool's purpose and output semantics.

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 specific action ('导出' meaning 'export') and resource ('当前完整的计划数据' meaning 'current complete plan data'), and distinguishes it from sibling tools by mentioning its complementary relationship with loadPlan for state restoration. It provides a precise verb+resource combination that differentiates it from other plan-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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('导出当前完整的计划数据' for exporting complete plan data) and mentions its relationship with loadPlan for state restoration, providing clear context. However, it doesn't specify when NOT to use it or explicitly contrast it with alternatives like getPlanStatus or getTaskList that provide partial plan information.

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/donway19/MCPlanManager'

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