Skip to main content
Glama
williamzujkowski

Strudel MCP Server

memory_usage

Monitor system memory consumption to optimize performance and prevent crashes during music pattern generation and live coding sessions.

Instructions

Get current memory usage statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'memory_usage' tool in the getTools() method, including name, description, and empty input schema (no parameters required).
    {
      name: 'memory_usage',
      description: 'Get current memory usage statistics',
      inputSchema: { type: 'object', properties: {} }
    },
  • Handler implementation in executeTool switch statement. Calls perfMonitor.getMemoryUsage() and returns the memory stats as JSON or fallback message.
    case 'memory_usage':
      const memory = this.perfMonitor.getMemoryUsage();
      return memory ? JSON.stringify(memory, null, 2) : 'Memory usage not available';
  • Core helper method that retrieves and formats Node.js process.memoryUsage() into human-readable MB values for heapUsed, heapTotal, RSS, and external memory.
    getMemoryUsage() {
      if (typeof process !== 'undefined' && process.memoryUsage) {
        const usage = process.memoryUsage();
        return {
          heapUsed: (usage.heapUsed / 1024 / 1024).toFixed(2) + ' MB',
          heapTotal: (usage.heapTotal / 1024 / 1024).toFixed(2) + ' MB',
          rss: (usage.rss / 1024 / 1024).toFixed(2) + ' MB',
          external: (usage.external / 1024 / 1024).toFixed(2) + ' MB'
        };
      }
      return null;
    }
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. While 'Get' implies a read operation, the description doesn't specify what kind of memory usage is measured (system, process, application), whether this requires special permissions, what format the statistics are returned in, or if there are any rate limits. This is inadequate for a diagnostic tool with zero annotation coverage.

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 perfectly concise at 5 words - a single sentence that directly states the tool's purpose with zero wasted words. It's front-loaded with the core functionality and doesn't include unnecessary elaboration.

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?

For a diagnostic tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'memory usage statistics' includes (RAM, swap, heap, etc.), what format the data is returned in, or how this tool relates to other diagnostic siblings. Given the complexity of system monitoring and the lack of structured documentation, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the baseline score is 4. The description appropriately doesn't waste space discussing parameters that don't exist, though it could optionally mention that no configuration is needed.

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 tool's purpose with a specific verb ('Get') and resource ('current memory usage statistics'). It distinguishes itself from siblings by focusing on system diagnostics rather than music generation or manipulation. However, it doesn't explicitly differentiate from other diagnostic tools like 'diagnostics' or 'status'.

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. There's no mention of when this tool is appropriate, what prerequisites might exist, or how it differs from sibling tools like 'diagnostics', 'performance_report', or 'status' that might also provide system information.

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/williamzujkowski/strudel-mcp-server'

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