Skip to main content
Glama

generate_progress_report

Create progress dashboards for writing projects by tracking word counts, analyzing manuscript directories, and monitoring completion against goals.

Instructions

Create progress dashboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathNoPath to manuscript directory (defaults to current directory)
target_word_countNoTarget word count goal
scopeNoFile scope pattern
include_todosNoInclude TODO count

Implementation Reference

  • The core handler function implementing generate_progress_report tool logic. Fetches writing stats and TODOs, computes progress percentage against optional target word count, and returns a summary report.
    private async generateProgressReport(args: Record<string, unknown>) {
      const targetWordCount = args.target_word_count as number | undefined;
      const scope = args.scope as string | undefined;
      const includeTodos = (args.include_todos as boolean) ?? true;
    
      const stats = await this.writersAid.getStats({ scope });
      const todos = includeTodos ? await this.writersAid.findTodos({}) : [];
    
      const progress = targetWordCount
        ? (stats.totalWords / targetWordCount) * 100
        : 0;
    
      return {
        totalWords: stats.totalWords,
        targetWordCount,
        progress: Math.round(progress),
        todosRemaining: includeTodos ? todos.length : undefined,
        filesCount: stats.totalFiles,
      };
    }
  • The JSON schema definition for the generate_progress_report tool, specifying input parameters like target_word_count, scope, and include_todos.
    {
      name: "generate_progress_report",
      description: "Create progress dashboard",
      inputSchema: {
        type: "object",
        properties: {
          project_path: { type: "string", description: "Path to manuscript directory (defaults to current directory)" },
          target_word_count: { type: "number", description: "Target word count goal" },
          scope: { type: "string", description: "File scope pattern" },
          include_todos: { type: "boolean", description: "Include TODO count", default: true },
        },
      },
    },
  • The dispatch case in WriterToolHandlers.handleTool() method that registers and routes calls to the generateProgressReport handler.
    case "generate_progress_report":
      return this.generateProgressReport(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create' implies a write operation, but the description doesn't state whether this generates a file, modifies existing data, requires specific permissions, or has side effects. It also doesn't mention output format, persistence, or any rate limits. For a creation tool with zero annotation coverage, this is a significant gap.

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 extremely concise with just two words. It's front-loaded with the core action and resource. However, it's arguably too brief, bordering on under-specified rather than efficiently informative.

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 complexity of creating a progress dashboard with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the dashboard contains, how it's presented, whether it's saved or temporary, or what the user can expect after invocation. The agent lacks sufficient context to understand the tool's full behavior and output.

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 four parameters with clear descriptions. The description adds no additional parameter information beyond what's in the schema. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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 'Create progress dashboard' states the action (create) and resource (progress dashboard), but is vague about what a 'progress dashboard' entails. It doesn't specify what metrics or visualizations are included, nor does it differentiate from sibling tools like 'get_writing_stats' or 'track_changes' that might provide related progress information.

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. The description doesn't mention prerequisites, appropriate contexts, or exclusions. With many sibling tools that could relate to progress tracking (e.g., 'get_writing_stats', 'track_changes', 'find_todos'), the agent has no indication of when this specific dashboard creation is preferred.

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/xiaolai/claude-writers-aid-mcp'

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