Skip to main content
Glama

docs_update

Update project documentation automatically after development changes by specifying modified files and change context to maintain accurate technical records.

Instructions

Update documentation after completing development work

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesArray of file paths that were modified
contextYesDescription of changes made
categoryNoPrimary category of work (optional, auto-detected if not provided)

Implementation Reference

  • The handler function for the 'docs_update' MCP tool. It receives input arguments and forwards them to the DocumentationService.processDocumentationRequest method with action set to 'update', which handles the actual documentation update logic.
    tools.set('docs_update', async (args: any) => {
      return await documentationService.processDocumentationRequest({
        action: 'update',
        files: args.files,
        context: args.context,
        category: args.category
      });
    });
  • The input schema definition for the 'docs_update' tool, specifying required files and context, optional category, used for MCP tool validation.
    {
      name: 'docs_update',
      description: 'Update documentation after completing development work',
      inputSchema: {
        type: 'object',
        properties: {
          files: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of file paths that were modified'
          },
          context: {
            type: 'string',
            description: 'Description of changes made'
          },
          category: {
            type: 'string',
            enum: ['frontend', 'backend', 'electron', 'database', 'testing'],
            description: 'Primary category of work (optional, auto-detected if not provided)'
          }
        },
        required: ['files', 'context']
      }
    },
  • src/index.ts:411-412 (registration)
    Registration of all documentation tools, including 'docs_update', into the main MCP tools map and toolDefinitions array in the primary server entry point.
    const docTools = registerDocumentationTools(this.tools, this.documentationService);
    this.toolDefinitions.push(...docTools);
  • Core helper method implementing the documentation update logic for action 'update'. Orchestrates updates to category READMEs, master documentation, and change history recording.
    private async updateDocumentation(context: DocumentationContext, changes: string): Promise<DocumentationResponse> {
      const updates: string[] = [];
      
      try {
        // Update category-specific documentation
        const categoryUpdates = await this.updateCategoryDocumentation(context, changes);
        updates.push(...categoryUpdates);
    
        // Update master documentation
        const masterUpdates = await this.updateMasterDocumentation(context, changes);
        updates.push(...masterUpdates);
    
        // Record change history
        await this.recordChangeHistory(context, changes);
        updates.push('Updated change history');
    
        return {
          success: true,
          updates,
          message: `Successfully updated ${updates.length} documentation sections`
        };
      } catch (error) {
        return {
          success: false,
          message: `Documentation update failed: ${(error as any).message}`
        };
      }
    }
  • Entry point in DocumentationService that dispatches to specific actions, calling updateDocumentation for the 'docs_update' tool's action.
    async processDocumentationRequest(request: DocumentationRequest): Promise<DocumentationResponse> {
      try {
        const context = this.buildDocumentationContext(request);
        
        if (request.action === 'reference') {
          return await this.referenceDocumentation(context);
        } else if (request.action === 'update') {
          return await this.updateDocumentation(context, request.context);
        } else {
          throw new Error(`Unknown action: ${request.action}`);
        }
      } catch (error: any) {
        return {
          success: false,
          message: `Documentation processing failed: ${error.message}`
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation (implying mutation) but doesn't address permissions, side effects, error handling, or what 'update' entails (e.g., overwriting, appending, versioning). For a mutation tool with zero 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without waste. It's appropriately sized for a tool with good schema coverage and no complex behavioral nuances to explain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters with full schema coverage but no annotations or output schema, the description is minimally adequate. It states the purpose but lacks behavioral context (e.g., mutation implications) and doesn't leverage the rich sibling tool context to guide usage. For a mutation tool in a crowded namespace, it should do more.

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 three parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema (e.g., no examples, no clarification on 'files' format or 'context' content). Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Update documentation') and context ('after completing development work'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'docs_reference', 'docs_validate', or 'update_document_lifecycle', which likely have overlapping documentation-related purposes.

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 minimal contextual guidance ('after completing development work') but offers no explicit when-to-use rules, no exclusions, and no alternatives among the many sibling documentation tools. Without this, an agent might struggle to choose between this and similar tools like 'docs_validate' or 'update_document_lifecycle'.

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