Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_process_signal_reference

Read-onlyIdempotent

Look up POSIX/Linux process signals: returns number, name, default action, description, and kill/trap command examples.

Instructions

Process Signal Reference. Look up the POSIX / Linux process-signal table (31 standard signals) — for each signal returns its number, symbolic name (SIGTERM, SIGKILL, SIGHUP…), default kernel action, description, common senders, trap/handler behaviour, and ready-to-run kill/trap command examples. The "operation" field selects the query mode: "lookup" filters the table by free text, signal number, category and platform; "byName"/"byNumber" return one signal; and "categories" lists the category buckets. Use it as a static cheatsheet — it does not send, trap, or deliver any signal and touches no process. Runs locally on a built-in dataset: read-only, non-destructive, offline, contacts no external service, and is rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoQuery mode. "lookup" filters the full table (uses query/category/platform); "byName" returns one signal (uses name); "byNumber" returns one signal (uses number/platform); "categories" lists category buckets (ignores other fields).lookup
queryNolookup only. Free-text filter matched against signal name, short name, number, description, default action and senders. A digit-only value matches the signal number exactly; a full SIG name matches that signal only. Empty returns all.
platformNolookup/byNumber. Selects per-platform signal numbers, which differ across architectures (e.g. SIGUSR1 is 10 on Linux, 30 on macOS/FreeBSD).linux
categoryNolookup only. Restricts results to one behaviour bucket. all returns every signal.all
nameNobyName only. Signal name with or without the SIG prefix, case-insensitive (e.g. SIGTERM, term).
numberNobyNumber only. Signal number to resolve on the chosen platform (e.g. 9 for SIGKILL on Linux).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the lookup succeeded.
operationNoThe operation that was executed, echoed back.
resultNoOperation-specific payload. lookup returns signals (array of signal entries) and total (integer); byName/byNumber return a single signal entry; categories returns a categories array of id/label/description. A signal entry has name, number, default (default kernel action), description, sender (array), traps, examples (kill and trap shell snippets), and optional notes.
Behavior5/5

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

Adds beyond annotations: read-only, non-destructive, offline, rate-limited. No contradictions.

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?

Concise, front-loaded, each sentence adds value. Slightly verbose but appropriate for complex tool.

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 purpose, modes, safety, offline nature, rate limits, and output schema mention. Fully adequate for complex 6-param tool with existing output schema.

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

Parameters4/5

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

With 100% schema coverage, baseline 3. Description adds detailed explanation of operation modes and cross-references parameter usage.

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?

States specific purpose: look up POSIX/Linux process signal table, returns comprehensive signal info. Clearly distinguishes from conversion and other linux tools.

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

Usage Guidelines4/5

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

Explicitly says use as static cheatsheet, does not send/deliver signals. Implies context but doesn't compare to sibling tools.

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/Jambozx/onlinecybertools-mcp-server'

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