Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
process_listB

List running processes sorted by CPU or memory with optional name, user, status, CPU/memory thresholds, system-process filtering, sort order and limit.

process_killC

Kill the process identified by the given PID

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: process_kill terminates a specific process by PID, while process_list provides a comprehensive overview of running processes with filtering and sorting options. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (process_kill and process_list), using the same prefix 'process_' and clear action verbs. This uniformity makes the tool set predictable and easy to understand.

Tool Count3/5

With only two tools, the server feels thin for a process management domain, as it lacks operations like process creation, monitoring, or detailed inspection. While the tools cover basic killing and listing, the scope is minimal and may limit agent capabilities in more complex scenarios.

Completeness2/5

The tool set is severely incomplete for process management. It includes kill and list operations but misses essential functions such as process creation, status updates, resource monitoring, or handling process groups. This will likely cause agent failures when tasks require more than basic termination or listing.

Maintenance

ActivityInactive
ResponsivenessUnresponsive