Skip to main content
Glama

generate_documentation_report

Generate documentation reports to analyze status, quality, lifecycle, connections, and duplicates for project documentation.

Instructions

Generate comprehensive reports on documentation status and quality

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportTypeYesType of report to generate
timeRangeNoTime range for the report
includeAINoInclude AI analysis in report

Implementation Reference

  • The core handler function for the 'generate_documentation_report' tool. It logs the report generation, dispatches to specific report generator functions based on the reportType parameter, handles errors, and returns a structured response including the report and timestamp.
    tools.set('generate_documentation_report', async (args: any) => {
      try {
        logger.info(`Generating ${args.reportType} report`);
        
        let report: any;
        
        switch (args.reportType) {
          case 'lifecycle':
            report = await generateLifecycleReport(args.timeRange, lifecycleService, dateTimeService);
            break;
          case 'quality':
            report = await generateQualityReport(args.includeAI, lifecycleService, aiService, dateTimeService);
            break;
          case 'connections':
            report = await generateConnectionsReport(connectionService, dateTimeService);
            break;
          case 'duplicates':
            report = await generateDuplicatesReport(lifecycleService, aiService, dateTimeService);
            break;
          case 'comprehensive':
            report = await generateComprehensiveReport(args.timeRange, args.includeAI, services);
            break;
          default:
            throw new Error(`Unknown report type: ${args.reportType}`);
        }
        
        return {
          success: true,
          reportType: args.reportType,
          report,
          generatedAt: localizationService.getCurrentDateTimeString()
        };
      } catch (error) {
        logger.error('Failed to generate documentation report:', error);
        throw error;
      }
    });
  • Zod schema providing TypeScript type safety and validation for the input parameters of the generate_documentation_report tool, including reportType, optional timeRange, and includeAI flag.
    export const GenerateDocumentationReportSchema = z.object({
      reportType: z.enum(['lifecycle', 'quality', 'connections', 'duplicates', 'comprehensive']),
      timeRange: z.object({
        start: z.string().datetime(),
        end: z.string().datetime(),
      }).optional(),
      includeAI: z.boolean().default(true),
    });
  • MCPTool registration definition for 'generate_documentation_report', including the tool name, description, and JSON Schema for input validation, returned as part of the enhancedTools array.
    {
      name: 'generate_documentation_report',
      description: 'Generate comprehensive reports on documentation status and quality',
      inputSchema: {
        type: 'object',
        properties: {
          reportType: {
            type: 'string',
            enum: ['lifecycle', 'quality', 'connections', 'duplicates', 'comprehensive'],
            description: 'Type of report to generate'
          },
          timeRange: {
            type: 'object',
            properties: {
              start: {
                type: 'string',
                description: 'Start date (ISO format)'
              },
              end: {
                type: 'string',
                description: 'End date (ISO format)'
              }
            },
            description: 'Time range for the report'
          },
          includeAI: {
            type: 'boolean',
            description: 'Include AI analysis in report',
            default: true
          }
        },
        required: ['reportType']
      }
    }
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. While 'generate comprehensive reports' implies a read-only operation that produces output, it doesn't specify whether this is a long-running process, what permissions are required, what format the report takes, or whether there are rate limits. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for the tool's complexity, though it could be slightly more front-loaded with key differentiators if they existed.

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 tool has no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain what the generated report contains, how it's delivered, or how it differs from other documentation analysis tools. For a report generation tool with behavioral unknowns, this leaves too many contextual gaps.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (reportType with enum values, timeRange with start/end dates, includeAI with default). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 for high schema coverage.

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 verb 'generate' and the resource 'comprehensive reports on documentation status and quality', making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'analyze_document_quality' or 'track_document_work', which might have overlapping functionality.

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 guidance on when to use this tool versus alternatives. With multiple documentation-related sibling tools available (e.g., analyze_document_quality, docs_search, track_document_work), there's no indication of what makes this tool distinct or when it should be preferred over others.

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/Ghostseller/CastPlan_mcp'

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