Skip to main content
Glama

List repair queue

list_supervisor_queue

Lists tasks requiring repair across standard and Intelligence modes so you can identify and address failed or incomplete work without triggering model calls.

Instructions

Tasks needing repair across standard and Intelligence modes. This tool makes no model calls.

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

Input Schema

NameRequiredDescriptionDefault
afterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose one genuinely useful trait — that the tool makes no model calls, so it is cheap and side-effect-free — but says nothing about whether the queue is filtered per account, how results are ordered, how large it can get, or how pagination terminates.

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 tight sentences with no filler and the domain scope front-loaded. The efficiency is somewhat hollow here because the length comes from omission rather than deliberate restraint, but the prose itself is clean and readable.

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

Completeness2/5

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

No output schema, no annotations, and an undocumented pagination parameter mean the description should explain what a queue entry looks like and how paging works; it does neither, leaving an agent unable to page reliably or know what fields to expect.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'after' parameter, so the description must compensate and does not. It never mentions the cursor semantics, whether 'after' is an ID or an offset, or that omitting it returns the head of the queue.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 'tasks needing repair across standard and Intelligence modes', which gives useful scope, but it never states the verb — that it lists or returns a queue — and the reader has to lean on the name and title to know this is a read/enumeration tool rather than a repair action.

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?

The mention of 'standard and Intelligence modes' implies coverage breadth and the note about no model calls hints at a cheap pre-check role, but there is no explicit when-to-use versus sibling tools such as get_supervisor_task, claim_supervisor_task, or apply_supervisor_task, and no statement of when not to call it.

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