Skip to main content
Glama

Check the queue

queue_status

Check whether the Clips Kitty queue is active, paused, or full so you can confirm if work is stalled before reporting that nothing is happening.

Instructions

What the queue is doing, how much room is left, and whether it is paused. Check this before reporting that nothing is happening.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the observable payload: activity, remaining room, and paused flag, which implies a non-mutating read. It could go further by saying whether the check is cheap, whether it blocks, or what shape the response takes, but the key behavioral traits are conveyed.

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?

Two short sentences, front-loaded with the reported fields and followed by the usage cue. The opening phrase 'What the queue is doing' is slightly informal where 'current queue activity' would be tighter, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must hint at return values, and it does so by naming the three reported dimensions. For a zero-parameter status tool that is close to sufficient; only the response format and relationship to sibling status tools remain unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs and instead describes what comes back.

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 states the resource and the three things it reports: current queue activity, remaining capacity, and paused state. That is a specific read-oriented purpose an agent can act on, though it never distinguishes itself from siblings like queue_local_file or queue_video, so sibling differentiation is left to inference.

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?

One concrete usage cue is given: check it before reporting that nothing is happening, which frames it as a diagnostic step. There is no explicit when-not guidance, no mention of alternatives such as job_status or engine_status, and no prerequisites, so the guidance is implied rather than complete.

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