Skip to main content
Glama

enqueue_feature

Queue a feature for a running continuous worker to process after it finishes its current task. Specify the project directory, worker ID, and feature ID to add work to the swarm.

Instructions

Add a feature to a running continuous worker's task queue. The worker will pick it up after finishing its current task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectDir": "<projectDir>",
      "workerId": "<workerId>",
      "featureId": "<featureId>"
    },
    "name": "enqueue_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerIdYesThe continuous worker's ID
featureIdYesFeature ID to add to the queue
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful execution semantics — the task is deferred until the worker finishes its current task — which is genuine behavioral context. It does not state what happens if the worker is not running, whether duplicate enqueues are rejected, or what the call returns.

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?

Two short sentences with the action front-loaded and the deferred-execution consequence immediately following. Nothing is redundant or padded.

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

Completeness3/5

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

For a three-parameter mutation tool with no annotations and no output schema, the description covers the core mechanic (enqueue for later pickup) but leaves out error conditions and the result of the call. It is adequate but not complete for an agent deciding whether the call will succeed.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (projectDir, workerId, featureId) are already documented in the schema. The description adds no additional meaning about formats or constraints, so the baseline of 3 applies.

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 uses a specific verb and resource: adding a feature to a running continuous worker's task queue. This is clearly distinct from generic feature mutation in the sense that the target is a worker's queue, though it never explicitly names the sibling add_feature or contrasts with it.

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 phrase 'running continuous worker's task queue' implies the worker must already be running, which is a usable precondition. However, there is no explicit when-to-use versus alternatives such as add_feature, and no stated exclusions or failure conditions.

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