Skip to main content
Glama

list

Retrieve all known background jobs—queued, running, or finished—ordered by most recent start, including queue positions and the current concurrency cap without blocking on job execution.

Instructions

List every background job the server currently knows about - queued, running, or finished - most-recently-started first. A queued job (admitted into the concurrency queue but not yet spawned - see run's own description) carries its queue_position; the current concurrency cap is included too. Never blocks on any job's own execution.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description supplies important behavior: it lists all known jobs across states, orders them, exposes queue_position for queued jobs, includes the concurrency cap, and guarantees it never blocks on a job's execution. It stops short of documenting permissions, pagination, or full return shape, but the non-blocking read behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads the action, resource, state scope, and ordering. The remaining sentences add only relevant queue semantics and the non-blocking guarantee, with no redundant restatement of the name.

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?

For a zero-parameter listing tool with no output schema, the description gives enough behavioral context to call it correctly: state coverage, ordering, queued-job queue_position, and concurrency cap. Remaining gaps are minor, mainly pagination or the full structure of each job entry.

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 has zero parameters, so the baseline is 4; there is no schema parameter meaning for the description to supplement. The queued-job and concurrency-cap details describe output/state rather than inputs, which is appropriate.

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?

States a specific verb and resource ('List every background job') and scopes it to queued, running, and finished jobs with most-recently-started ordering. It is clear without opening a schema, though it does not explicitly name a sibling alternative such as status for a single-job lookup.

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?

Implies usage for a non-blocking overview of all jobs and references run's description for queued-job semantics. It does not explicitly say when to use list versus status, follow, output, or tail, so alternatives are left to inference.

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

Deploy Server

Other Tools