Skip to main content
Glama

profile_cpu

Read-onlyIdempotent

Identifies which RouterOS processes consume CPU by sampling usage over a few seconds, helping diagnose high CPU load on MikroTik devices.

Instructions

Shows which RouterOS processes use the CPU, sampled over a few seconds.

Notes: cpu: "total" (default), "all" for one column per core, or a core number (a duration under 3 runs for 3).

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": "profile_cpu"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpuNo
deviceNo
durationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.1

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real behavior beyond them by disclosing that measurement is sampled over a few seconds rather than instantaneous, which affects how the agent should interpret the result.

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

Conciseness4/5

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

The core purpose is front-loaded in the first sentence and the parameter note is short and separate. The parenthetical about duration is garbled and hard to parse, which costs a point, but there is no padding overall.

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?

An output schema exists, so return values need not be explained. However, for a 3-parameter tool with zero schema descriptions, leaving the device parameter entirely undocumented and the duration semantics ambiguous leaves a real gap an agent must guess through.

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 0%, so the description carries the full burden and it only partly succeeds. It explains the cpu parameter's accepted values concretely ("total", "all" for per-core columns, or a core number) and hints at the duration/cpu interaction, but the device parameter is never mentioned at all.

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 gives a specific verb and resource: it shows which RouterOS processes are consuming CPU, sampled over a few seconds. That is far more informative than the bare name profile_cpu. It does not differentiate against any alternative profiling tool, but none of the listed siblings appears to overlap.

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

Usage Guidelines3/5

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

Usage is only implied: the sampling behavior suggests a live diagnostic use case, but the description never states when an agent should call this versus other diagnostics. There are no exclusions or prerequisites, and no named alternative.

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

Deploy Server

Other Tools