Skip to main content
Glama
caseSHY

caseSHY/aicoreutils

by caseSHY
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

nice

Read-only

Adjust CPU scheduling priority for a command to reduce CPU impact. Execute with niceness adjustment, capture output, and enforce a safety timeout.

Instructions

Run a command with adjusted CPU scheduling priority (niceness). Executes the given command as a subprocess, captures bounded stdout/stderr, and enforces a safety timeout. Use --dry_run to preview without execution. Positive niceness lowers priority for background tasks; negative values may require elevated privileges. Use to reduce CPU impact of background work. Not for I/O buffering control — use 'stdbuf'. Not for hangup immunity — use 'nohup'. Not for time-bound execution — use 'timeout'. See also 'stdbuf', 'nohup', 'timeout'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adjustmentNoNiceness adjustment.
command_argsNoCommand and arguments to run.
dry_runNoReport without running the command.
max_output_bytesNoMaximum captured stdout/stderr bytes each.
timeoutNoSafety timeout for the command.

Tool Definition Quality

A3.9/5.0
Behavior1/5

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

Description contradicts annotations: readOnlyHint=true but description says it runs a command, which implies potential mutation. Annotation contradiction flag set.

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, front-loaded with purpose, then details. No wasted sentences.

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?

Covers execution behavior, output capturing, timeout, dry-run, niceness privileges, and references to sibling tools despite no output schema.

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 coverage is 100%, description does not add parameter-specific info beyond what's in schema. Baseline 3.

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?

Description clearly states the tool runs a command with adjusted niceness, distinguishing from siblings like stdbuf, nohup, timeout.

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 (reduce CPU impact of background tasks) and lists alternatives for other use cases (I/O buffering, hangup immunity, time-bound execution).

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/caseSHY/AI-CLI'

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