Skip to main content
Glama

process_umb_command

Execute the Update Memory Bank (UMB) command to manage and update the central knowledge base on the MCP server with SSH support.

Instructions

Processes the Update Memory Bank (UMB) command

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesComplete UMB command

Implementation Reference

  • The main handler function that implements the process_umb_command tool logic: validates memory bank, checks UMB trigger in command, activates UMB mode if valid.
    export function handleProcessUmbCommand(memoryBankManager: MemoryBankManager, command: string) {
      if (!memoryBankManager.getMemoryBankDir()) {
        return {
          content: [
            {
              type: 'text',
              text: 'Memory Bank not found. Use initialize_memory_bank to create one.',
            },
          ],
          isError: true,
        };
      }
      
      const isUmbTrigger = memoryBankManager.checkUmbTrigger(command);
      
      if (!isUmbTrigger) {
        return {
          content: [
            {
              type: 'text',
              text: 'Invalid UMB command. Use "Update Memory Bank" or "UMB".',
            },
          ],
          isError: true,
        };
      }
      
      const success = memoryBankManager.activateUmbMode();
      
      if (!success) {
        return {
          content: [
            {
              type: 'text',
              text: 'Failed to activate UMB mode. Check if the current mode supports UMB.',
            },
          ],
          isError: true,
        };
      }
      
      return {
        content: [
          {
            type: 'text',
            text: '[MEMORY BANK: UPDATING] UMB mode activated. You can temporarily update Memory Bank files.',
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema requiring a 'command' string.
    {
      name: 'process_umb_command',
      description: 'Processes the Update Memory Bank (UMB) command',
      inputSchema: {
        type: 'object',
        properties: {
          command: {
            type: 'string',
            description: 'Complete UMB command',
          },
        },
        required: ['command'],
      },
    },
  • Registers the tool for discovery by including it in the modeTools array within the list of all tools handled by ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        ...coreTools,
        ...progressTools,
        ...contextTools,
        ...decisionTools,
        ...modeTools,
      ],
    }));
  • Dispatches calls to the process_umb_command tool by extracting arguments and invoking the handleProcessUmbCommand handler in the main tool call switch statement.
    case 'process_umb_command': {
      const { command } = request.params.arguments as { command: string };
      if (!command) {
        throw new McpError(ErrorCode.InvalidParams, 'Command not specified');
      }
      return handleProcessUmbCommand(memoryBankManager, command);
    }
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. It only states 'Processes', implying a mutation or action, but doesn't disclose behavioral traits such as side effects, permissions needed, error handling, or what 'processing' entails operationally, leaving significant 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 with no wasted words, making it appropriately sized. However, it's front-loaded with minimal content, which limits its helpfulness despite being concise.

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 annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'processing' involves, the return values, or how it fits with siblings, failing to provide enough context for effective use.

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 schema description coverage is 100%, with the parameter 'command' documented as 'Complete UMB command'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from 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 states the tool 'Processes the Update Memory Bank (UMB) command', which provides a basic verb+resource (process + UMB command). However, it's vague about what processing entails and doesn't differentiate from siblings like 'complete_umb' or 'update_active_context', leaving ambiguity about its specific role.

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. With siblings like 'complete_umb' and 'update_active_context' that might overlap, the description lacks context, prerequisites, or exclusions, offering no help for 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

Related 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/aakarsh-sasi/memory-bank-mcp'

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