Skip to main content
Glama
williamzujkowski

Strudel MCP Server

performance_report

Analyze performance metrics and identify bottlenecks in Strudel music patterns to optimize computational efficiency and audio generation.

Instructions

Get performance metrics and bottlenecks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'performance_report' tool. Calls PerformanceMonitor.getReport() and getBottlenecks(5) to generate the response.
    case 'performance_report':
      const report = this.perfMonitor.getReport();
      const bottlenecks = this.perfMonitor.getBottlenecks(5);
      return `${report}\n\nTop 5 Bottlenecks:\n${JSON.stringify(bottlenecks, null, 2)}`;
  • Tool registration in getTools() method, including name, description, and input schema.
    {
      name: 'performance_report',
      description: 'Get performance metrics and bottlenecks',
      inputSchema: { type: 'object', properties: {} }
    },
  • PerformanceMonitor.getReport() method generates the formatted performance metrics table used by the tool.
    getReport(): string {
      const metrics = this.getMetrics() as any[];
      if (!metrics || metrics.length === 0) {
        return 'No performance metrics collected';
      }
    
      let report = '\n=== PERFORMANCE REPORT ===\n\n';
      report += 'Operation'.padEnd(30) + 'Calls'.padEnd(10) + 'Avg(ms)'.padEnd(12) + 'Min(ms)'.padEnd(12) + 'Max(ms)'.padEnd(12) + 'Errors\n';
      report += '-'.repeat(86) + '\n';
    
      metrics.forEach(m => {
        report += m.operation.padEnd(30) +
                  m.calls.toString().padEnd(10) +
                  m.averageTime.toFixed(2).padEnd(12) +
                  m.minTime.toFixed(2).padEnd(12) +
                  m.maxTime.toFixed(2).padEnd(12) +
                  `${m.errorRate.toFixed(1)}%\n`;
      });
    
      const totalCalls = metrics.reduce((sum, m) => sum + m.calls, 0);
      const totalTime = metrics.reduce((sum, m) => sum + m.totalTime, 0);
    
      report += '\n';
      report += `Total Operations: ${totalCalls}\n`;
      report += `Total Time: ${totalTime.toFixed(2)}ms\n`;
      report += `Average per Operation: ${(totalTime / totalCalls).toFixed(2)}ms\n`;
    
      return report;
  • PerformanceMonitor.getBottlenecks() identifies top slowest operations for the bottlenecks section.
    getBottlenecks(limit: number = 5) {
      const metrics = this.getMetrics() as any[];
      return metrics
        .sort((a, b) => b.averageTime - a.averageTime)
        .slice(0, limit)
        .map(m => ({
          operation: m.operation,
          averageTime: m.averageTime.toFixed(2) + 'ms',
          maxTime: m.maxTime.toFixed(2) + 'ms',
          calls: m.calls
        }));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'metrics and bottlenecks' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, what format the output takes, or if it has side effects (e.g., logging). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise ('Get performance metrics and bottlenecks')—a single phrase with no wasted words. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 implied by 'performance metrics and bottlenecks' and the lack of annotations and output schema, the description is incomplete. It doesn't explain what metrics are included, how bottlenecks are identified, or what the return values look like, leaving the agent with insufficient context to use the tool effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for, and it avoids misleading information.

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 'Get performance metrics and bottlenecks' states a clear purpose (retrieving performance data) but is vague about scope and resource. It doesn't specify what system or component's performance is being measured, nor does it distinguish from sibling tools like 'diagnostics', 'status', or 'memory_usage' which might overlap with performance monitoring.

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 'diagnostics' (for troubleshooting), 'status' (for system state), and 'memory_usage' (for resource monitoring), the description lacks context on whether this is for real-time metrics, historical analysis, or specific performance aspects, leaving usage ambiguous.

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