Skip to main content
Glama

get_top_processes

List top processes by CPU or memory usage to identify resource hogs on your system.

Instructions

List the top resource-consuming processes sorted by CPU or memory usage.

Use this to identify which processes are consuming the most resources. Use sort_by="memory" (default) to find memory hogs, or sort_by="cpu" to find CPU-intensive processes. Use get_system_overview first for the big picture, then this tool to drill down into specific processes. To search for a specific process by name, use find_process instead.

This is a read-only operation with no side effects. When sorting by CPU, takes ~0.5 seconds for accurate sampling; memory sorting is instant.

Returns a Markdown table with columns: PID, Name, CPU%, Mem%, RSS, Status. Processes that exit during enumeration or require elevated access are skipped.

Args: sort_by: Sort criterion — "cpu" for CPU usage or "memory" for RAM usage. Default: "memory". Any value other than "cpu" is treated as "memory". limit: Maximum number of processes to return. Range: 1-50. Default: 10. Values outside the range are clamped automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sort_byNomemory
Behavior5/5

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

No annotations, so description fully covers: declares read-only with no side effects, notes timing differences (CPU ~0.5s, memory instant), and mentions skipped processes (exited or elevated access).

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?

Well-structured: purpose first, then usage guidelines, behavioral notes, parameter details. Each sentence adds value, no fluff.

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

Completeness5/5

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

Without output schema, description explains return format (Markdown table with columns). Covers all relevant aspects: purpose, usage context, behavior, parameters, and output.

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

Parameters5/5

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

Schema has 0% coverage, but description explains both parameters: sort_by accepts 'cpu' or 'memory' (default behavior), limit 1-50 with clamping. Adds meaning beyond schema defaults.

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?

Clearly states it lists top resource-consuming processes sorted by CPU or memory. Distinguishes from siblings: directs to get_system_overview for big picture and find_process for specific search.

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

Usage Guidelines5/5

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

Explicitly says when to use (drill down after overview) and when not (use find_process for specific process). Also explains sort_by options and behavior.

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/dragogargo/mcp-sysmon'

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