Skip to main content
Glama

getLoadAverage

Monitor system performance by retrieving load averages for 1, 5, and 15-minute intervals to assess CPU utilization and resource demands.

Instructions

Get system load average for 1, 5, and 15 minutes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the getLoadAverage tool. It calls os.loadavg() to retrieve the 1, 5, and 15-minute load averages and formats them as JSON in the MCP response content.
    handler: async () => {
      const [oneMin, fiveMin, fifteenMin] = os.loadavg();
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            oneMinute: oneMin,
            fiveMinutes: fiveMin,
            fifteenMinutes: fifteenMin
          }, null, 2)
        }]
      };
    }
  • Tool metadata including name, description, and input schema (no parameters required).
    getLoadAverage: {
      name: 'getLoadAverage',
      description: 'Get system load average for 1, 5, and 15 minutes',
      inputSchema: {
        type: 'object',
        properties: {}
      },
  • src/index.ts:28-35 (registration)
    Registers the getLoadAverage tool by spreading systemTools into the allTools object, which is used by the MCP server's listTools and callTool request handlers.
    const allTools: ToolKit = {
      ...systemTools,
      ...networkTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
  • src/index.ts:5-5 (registration)
    Imports the systemTools object containing the getLoadAverage tool definition.
    import { systemTools } from './tools/system.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool returns but doesn't mention whether this requires special permissions, whether it's a read-only operation, what format the data comes in, or any rate limits. The description provides basic functionality but lacks important behavioral context.

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 communicates the complete purpose without any wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point.

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?

For a simple read-only tool with no parameters and no output schema, the description adequately explains what the tool does. However, without annotations or output schema, it could benefit from mentioning the return format (e.g., array of three numbers) or typical use cases to provide more complete context.

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 schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, which is correct for this tool configuration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get system load average') and the exact resources being retrieved ('for 1, 5, and 15 minutes'). It distinguishes itself from sibling tools like 'getSystemInfo' by focusing specifically on load average metrics rather than broader system information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (monitoring system performance metrics) but doesn't explicitly state when to use this tool versus alternatives like 'getSystemInfo' or other monitoring tools. No guidance is provided about when not to use it or about prerequisites.

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/cyanheads/toolkit-mcp-server'

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