Skip to main content
Glama
JackXuyi

Current operating environment

getProcesses

Retrieve active process information from the current operating environment to monitor system activity and identify running applications.

Instructions

获取当前设备的进程信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'getProcesses' tool. It uses the 'systeminformation' library (si.processes()) to fetch current system processes and returns them as a JSON string in the tool response format.
    case "getProcesses": {
      const processes = await si.processes();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(processes, null, 2)
        }]
      };
    }
  • src/index.ts:208-216 (registration)
    Registration of the 'getProcesses' tool in the listTools response, including name, description, and empty input schema.
    {
      name: "getProcesses",
      description: "获取当前设备的进程信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema for the 'getProcesses' tool, which expects no parameters.
    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 full burden. While '获取' implies a read operation, it doesn't disclose whether this requires special permissions, what format the process information returns, whether it includes all processes or filtered ones, or any rate limits. For a system information tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple, parameterless tool and gets straight to the point without unnecessary elaboration.

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 the tool has no parameters, no annotations, and no output schema, the description provides the minimum viable information about what the tool does. However, for a system information tool among many similar siblings, it should ideally provide more context about what 'process information' includes and how it differs from other system monitoring tools. The description is complete enough to understand the basic purpose but lacks depth for optimal agent decision-making.

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 is 4. The description doesn't need to explain parameters since none exist, and it correctly doesn't mention any. The description focuses appropriately on what the tool does rather than parameter details.

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 verb ('获取' - get/retrieve) and resource ('当前设备的进程信息' - current device's process information). It distinguishes from siblings by focusing specifically on processes rather than other system information like CPU, memory, or network. However, it doesn't explicitly differentiate from potential similar tools (none exist in siblings).

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 retrieving different types of system information (CPU, memory, network, etc.), there's no indication that this is specifically for process information rather than other system metrics. No exclusions, prerequisites, or alternative tools are mentioned.

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