Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REDIS_URLNoRedis connection stringredis://localhost:6379/0
RQ_MCP_MODENo'readonly', 'write', or 'admin' — see Modesreadonly
RQ_MCP_WORKER_TTL_SNohealth_check's WORKER_STALE_HEARTBEAT threshold (matches RQ's own default worker TTL)420
RQ_MCP_TASK_WHITELISTNoPath to a TOML file listing functions enqueue_task may enqueue (write mode). Unset/missing/unparseable all mean nothing is enqueueable.
RQ_MCP_HIGH_FAILURE_THRESHOLDNohealth_check's HIGH_FAILURE_COUNT threshold50
RQ_MCP_OLDEST_JOB_THRESHOLD_SNohealth_check's OLDEST_JOB_TOO_OLD threshold300

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_rq_infoA

Return basic information about the Redis/RQ environment.

Includes Redis connection status, Redis/RQ versions, discovered queue names, and the number of active workers.

redis_infoA

Return selected Redis INFO fields.

Defaults to memory, clients, stats, and keyspace sections: used_memory, maxmemory, maxmemory_policy, evicted_keys, connected_clients, and per-database key counts. Unrecognized section names are ignored and listed in ignored_sections rather than raising an error.

list_queuesA

List all discovered RQ queues.

Returns, per queue: job counts by status (queued, started, finished, failed, deferred, scheduled, canceled) and the number of workers currently listening to it.

get_queueA

Return detailed status for a single queue by name.

Includes the same per-status counts as list_queues, the age in seconds of the oldest still-queued job (null if empty), and default_timeout in seconds (reflects this server's own default, since RQ does not persist a per-queue default_timeout to Redis). An unknown queue name is not an error -- RQ queues are lazy/virtual, so it returns the same shape with all counts at 0.

get_jobA

Return full details for a single RQ job by ID, or null if it does not exist.

Includes status, origin queue, function name, redacted/truncated args/kwargs/meta, timeout, ttl, dependency IDs, worker name, and lifecycle timestamps. Does not include the job's result or exception info -- use get_job_result for that.

get_job_resultA

Return a job's result/exc_info, or null if the job does not exist.

Truncated to max_bytes, with a truncated flag when that happened.

list_jobsA

List jobs in a queue filtered by status.

status must be one of: queued, started, finished, failed, deferred, scheduled, canceled. Returns up to limit (max 100) job summaries (id, function name, description, status, enqueued_at, started_at, ended_at) starting at offset, plus the total number of jobs at that status in the queue.

summarize_failuresA

Group a queue's failed jobs by function name + exception type.

Scans up to limit failed jobs (default 200) and returns one entry per (function, exception type) group: count, an example job ID, and first/last failure timestamps.

list_scheduled_jobsA

List scheduled jobs in a queue: id, function name, and scheduled time.

Returns up to limit (max 100) entries starting at offset, plus the total number of scheduled jobs in the queue.

list_workersA

List currently registered RQ workers, optionally filtered by queue.

Returns, per worker: name, state (idle/busy/started/suspended), the queue names it listens to, the ID of the job it's currently processing (if any), last heartbeat and its age in seconds, and its successful/failed job counters. If queue is given, only workers listening to that queue are returned.

get_workerA

Return full details for a single worker by name, or null if not currently registered.

Includes state, hostname, IP address, PID, queue names, current job ID (if any), birth/last-heartbeat timestamps (plus heartbeat age in seconds), job counters, and total working time in seconds.

health_checkA

Run read-only diagnostics across queues, workers, and Redis itself.

Returns {"ok": bool, "findings": [...]}; findings is empty and ok is true when nothing is wrong. Each finding has a severity, a stable code (QUEUE_NO_WORKERS, WORKER_STALE_HEARTBEAT, ORPHANED_STARTED_JOB, OLDEST_JOB_TOO_OLD, REDIS_EVICTION_RISK, HIGH_FAILURE_COUNT), a human-readable message, and structured details.

Prompts

Interactive templates invoked by user choice

NameDescription
diagnose_queue
triage_failed_jobs
why_is_job_stuck
capacity_check
post_deploy_check

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct RQ resource or view: environment info, Redis internals, queues, jobs, results, workers, failures, and health. The only close pair is list_jobs with status=scheduled and list_scheduled_jobs, but their return shapes and descriptions make the intended use clear.

Naming Consistency4/5

The naming is mostly predictable with get_ for single entities and list_ for collections, all in snake_case. summarize_failures and health_check deviate slightly from the get_/list_ pattern but remain readable and consistent in style.

Tool Count5/5

Twelve tools is well-scoped for an RQ monitoring and inspection server. Each tool covers a meaningful part of the domain without unnecessary redundancy or bloat.

Completeness5/5

The tool surface covers the major RQ monitoring areas: environment, Redis health, queues, jobs by status, individual job details and results, scheduled jobs, workers, failure aggregation, and health diagnostics. For a read-only monitoring server, there are no obvious dead ends or missing core operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues