Skip to main content
Glama
JackXuyi

Current operating environment

getMemoryInfo

Retrieve current system memory usage details including available, used, and total memory to monitor resource allocation and performance.

Instructions

获取当前系统的内存信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the getMemoryInfo tool. It calculates total memory, free memory, and used memory using Node.js 'os' module functions and returns the information as a JSON-formatted text response.
    case "getMemoryInfo": {
      const memoryInfo = {
        totalMemory: os.totalmem(),
        freeMemory: os.freemem(),
        usedMemory: os.totalmem() - os.freemem()
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(memoryInfo, null, 2)
        }]
      };
    }
  • src/index.ts:37-45 (registration)
    Registration of the getMemoryInfo tool in the list of tools provided by the handleRequest function, including its name, description, and input schema (which is an empty object).
    {
      name: "getMemoryInfo",
      description: "获取当前系统的内存信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema definition for the getMemoryInfo tool, specifying an empty object with no properties or requirements.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
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 of behavioral disclosure. While '获取' (get) implies a read-only operation, the description doesn't specify what memory information is returned (total, used, free, etc.), format of the output, whether this requires special permissions, or any rate limits. For a system information tool with zero annotation coverage, this is insufficient.

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 directly states the tool's purpose without any wasted words. It's appropriately sized for a simple, parameterless tool 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?

Given this is a simple read-only system information tool with no parameters and no output schema, the description is adequate but minimal. It states what information is retrieved but doesn't provide enough context about the output format or how this fits with the broader system monitoring toolset. The lack of annotations means the description should do more to explain behavioral aspects.

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 zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and it correctly focuses on what the tool does rather than trying to explain non-existent inputs.

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 as '获取当前系统的内存信息' (Get current system memory information), which is a specific verb+resource combination. However, it doesn't distinguish this from sibling tools like getCpuInfo or getDiskUsage, which follow the same pattern for different system resources.

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. With many sibling tools that retrieve different types of system information (CPU, disk, network, etc.), there's no indication of when memory information specifically is needed or how this tool relates to other system monitoring tools.

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/JackXuyi/env-mcp'

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