MCP Mac Monitor

Procesos con más consumo

get_top_processes

Read-only

Find which processes use the most CPU or memory right now, sortable by either metric, with an adjustable limit.

Instructions

Procesos que más CPU o memoria consumen en este momento.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_processes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Cuántos procesos devolver
`sort_by`	No	Ordenar por uso de CPU o de memoria	cpu

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already supply readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds 'en este momento', clarifying that this returns a live, current-time snapshot rather than a historical or continuous report. This temporal scoping adds value beyond the annotations without contradicting them.

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, front-loaded with the core purpose. Every word contributes; there is no redundant text or boilerplate.

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?

There is no output schema, so the description would ideally mention what fields each returned process includes (name, PID, CPU/memory values). The lack of return format info and no mention of default limit/organization could leave an agent guessing about downstream use. It is adequate but with a clear gap.

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

Parameters3/5

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

Schema description coverage is 100%: limit and sort_by already have clear descriptions including defaults, bounds, and the cpu/memory enum. The description simply echoes 'CPU o memoria' and does not add format, precedence, or edge-case semantics beyond the schema, so it remains at the baseline.

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 states a specific verb and resource: 'Procesos que consumen CPU o memoria en este momento' makes it clear this returns a current list of top processes by CPU or memory. It is distinct from siblings like get_cpu/get_memory (system metrics) though it does not explicitly name them, so it misses the highest tier of own-sibling differentiation.

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 for when to use this tool versus alternatives. The phrase 'en este momento' implies a current snapshot but never mentions when a user should prefer this over get_cpu, get_memory, or another sibling. No exclusions or alternative routing is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server