Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

list_processes

List all currently running processes to identify and manage system tasks.

Instructions

List processes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYes

Implementation Reference

  • The handler function that lists all running processes using the 'ps-list' npm package. It sorts processes by CPU usage, formats the top 50 with pid, name, cpu%, memory, ppid, and cmd, and returns them.
    async function listProcesses() {
      try {
        // Dynamic import for ES module ps-list
        const psList = (await import('ps-list')).default;
        const processes = await psList();
    
        // Sort by CPU usage
        processes.sort((a, b) => (b.cpu || 0) - (a.cpu || 0));
    
        // Format the output
        const formattedProcesses = processes.slice(0, 50).map(proc => ({
          pid: proc.pid,
          name: proc.name,
          cpu: proc.cpu ? `${proc.cpu.toFixed(1)}%` : '0.0%',
          memory: proc.memory ? `${(proc.memory / 1024 / 1024).toFixed(1)} MB` : '0.0 MB',
          ppid: proc.ppid,
          cmd: proc.cmd
        }));
    
        return {
          success: true,
          processes: formattedProcesses,
          total: processes.length,
          showing: formattedProcesses.length
        };
    
      } catch (error) {
        logger.error(`Error listing processes: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
  • Registration of the 'list_processes' tool in the MCP server's tool list, defining its name, description, and input schema (a dummy required field).
    { name:'list_processes', description:'List processes', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
  • Dispatch case in the MCP server's main switch statement that calls terminalTools.listProcesses() when the tool is invoked.
    case 'list_processes': data = await terminalTools.listProcesses(); break;
  • Export of the listProcesses function from the terminal_tools module, making it available to the MCP server via require.
    listProcesses,
Behavior1/5

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

No annotations exist, and the description provides zero behavioral details—no mention of side effects, permissions, or scope. The description is too minimal to inform an AI agent about what happens when the tool is invoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two words, which is under-specification rather than effective conciseness. No structure or additional information is provided to justify the brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and the generic description, the tool definition is incomplete. The agent has no understanding of return values or how 'processes' is defined, making it nearly unusable.

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

Parameters1/5

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

The input schema has one required parameter 'random_string' with no description, and the tool description does not explain it. With 0% schema description coverage, the description should compensate but fails entirely.

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

Purpose2/5

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

The description 'List processes' is a tautology of the tool name and provides no specifics about which processes are listed (system, project, etc.). It fails to distinguish from sibling tools like 'kill_process', which implies process management context.

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 given on when to use this tool or when to use alternatives. The description lacks context for appropriate usage scenarios.

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/FutureAtoms/agentic-control-framework'

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