Skip to main content
Glama

format_as_plan

Transform content into structured plans with prioritized steps, time estimates, and progress tracking checkboxes for clear task organization.

Instructions

as a plan|organize|checklist|format as plan|make a plan|organize this|checklist - Format content into clear plans

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent to format as a plan
priorityNoDefault priority level
includeTimeEstimatesNoInclude time estimates for each step
includeCheckboxesNoInclude checkboxes for tracking progress

Implementation Reference

  • Main handler function that parses input content into numbered plan steps with priorities, time estimates, checkboxes, and summary statistics.
    export async function formatAsPlan(args: { content: string; priority?: string; includeTimeEstimates?: boolean; includeCheckboxes?: boolean }): Promise<ToolResult> {
      const { content: planContent, priority = 'medium', includeTimeEstimates = true, includeCheckboxes = true } = args;
      
      // Parse content into actionable steps
      const sentences = planContent.split(/[.!?]+/).filter(s => s.trim().length > 10);
      const planSteps = sentences.map((sentence, index) => {
        const stepNumber = index + 1;
        const cleanSentence = sentence.trim();
        
        // Estimate time based on content complexity
        let timeEstimate = '5min';
        if (cleanSentence.length > 100) timeEstimate = '15min';
        else if (cleanSentence.length > 50) timeEstimate = '10min';
        
        // Detect priority keywords
        let stepPriority = priority;
        if (cleanSentence.match(/urgent|critical|important|first|must/i)) stepPriority = 'high';
        else if (cleanSentence.match(/later|eventually|nice|optional/i)) stepPriority = 'low';
        
        // Format step
        let formattedStep = includeCheckboxes ? `${stepNumber}. □ ` : `${stepNumber}. `;
        formattedStep += cleanSentence;
        if (includeTimeEstimates) formattedStep += ` (${stepPriority.toUpperCase()}, ${timeEstimate})`;
        
        return {
          number: stepNumber,
          content: cleanSentence,
          priority: stepPriority,
          timeEstimate,
          formatted: formattedStep
        };
      });
      
      // Calculate total time
      const totalMinutes = planSteps.reduce((total: number, step: any) => {
        const minutes = parseInt(step.timeEstimate.replace('min', ''));
        return total + minutes;
      }, 0);
      
      const planResult = {
        action: 'format_as_plan',
        originalContent: planContent,
        formattedPlan: planSteps.map((s: any) => s.formatted).join('\n'),
        steps: planSteps.length,
        totalEstimatedTime: `${totalMinutes} minutes`,
        breakdown: {
          high: planSteps.filter((s: any) => s.priority === 'high').length,
          medium: planSteps.filter((s: any) => s.priority === 'medium').length,
          low: planSteps.filter((s: any) => s.priority === 'low').length
        },
        status: 'success'
      };
      
      return {
        content: [{ type: 'text', text: `${planResult.formattedPlan}\n\nTotal: ${planResult.totalEstimatedTime} | Priority: ${planResult.breakdown.high}H ${planResult.breakdown.medium}M ${planResult.breakdown.low}L` }]
      };
    }
  • Tool schema definition including input schema with content (required), optional priority, time estimates, and checkboxes.
    export const formatAsPlanDefinition: ToolDefinition = {
      name: 'format_as_plan',
      description: 'as a plan|organize|checklist|format as plan|make a plan|organize this|checklist - Format content into clear plans',
      inputSchema: {
        type: 'object',
        properties: {
          content: { type: 'string', description: 'Content to format as a plan' },
          priority: { type: 'string', description: 'Default priority level', enum: ['high', 'medium', 'low'] },
          includeTimeEstimates: { type: 'boolean', description: 'Include time estimates for each step' },
          includeCheckboxes: { type: 'boolean', description: 'Include checkboxes for tracking progress' }
        },
        required: ['content']
      },
      annotations: {
        title: 'Format as Plan',
        audience: ['user', 'assistant']
      }
    };
  • src/index.ts:626-627 (registration)
    Dispatch case in the tool execution switch statement that calls the formatAsPlan handler.
    case 'format_as_plan':
      return await formatAsPlan(args as any) as CallToolResult;
  • src/index.ts:118-118 (registration)
    Inclusion of formatAsPlanDefinition in the tools array for MCP tool listing.
    formatAsPlanDefinition,
Behavior3/5

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

Annotations only provide a title ('Format as Plan'), so the description carries the full burden of behavioral disclosure. It mentions formatting into 'clear plans' but doesn't specify output format (e.g., markdown, plain text), whether it's read-only or mutates data, or any constraints like rate limits. The description adds minimal context beyond the title, leaving gaps in behavioral understanding.

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 brief and front-loaded with the core purpose, but the list of synonyms ('as a plan|organize|checklist...') is somewhat redundant and could be more structured. It's efficient overall, with no wasted sentences, though it could be slightly more polished.

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 no output schema and minimal annotations, the description is incomplete. It doesn't explain what the tool returns (e.g., formatted text, structured data), and with 4 parameters and sibling tools that might overlap, more context is needed for the agent to use it effectively. The description fails to compensate for the lack of structured output information.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaning beyond what's in the schema—it doesn't explain how parameters interact (e.g., how 'priority' affects the plan) or provide usage examples. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Format content into clear plans' which indicates its purpose, but it's vague about what constitutes a 'plan' and doesn't distinguish from sibling tools like 'break_down_problem', 'create_thinking_chain', or 'step_by_step_analysis' that might have overlapping functionality. The list of synonyms ('as a plan|organize|checklist|format as plan|make a plan|organize this|checklist') adds some context but doesn't clarify the specific verb+resource combination.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, and with many sibling tools that might handle similar tasks (e.g., 'break_down_problem', 'create_thinking_chain'), the agent is left without clear direction on tool selection.

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/ssdeanx/ssd-ai'

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