Skip to main content
Glama
Sign In
Task Queue MCP

Task Queue MCP

by devops-riku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read a task

get_task
Read-only

Retrieve a task by number or ID to review its description, comments, files, subtasks, and update rules before working on it or handling a reassignment.

Instructions

A task with its description, notes (comments), files, parent and subtasks, and how_to_update: the rules for changing it in its current state. reassigned is set when it reached its assignee from someone else’s queue: then read its comments before working on it, since they say what was done and found before the hand-off. Finds any task you may see by its number (pool tasks too, with View all tasks).

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": {
      "task": "<task>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task: its number, e.g. TASK-000123, or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known; the description goes further by listing the payload fields and explaining the meaning of the 'reassigned' flag and 'how_to_update'. It does not cover size/pagination or failure behavior for an unknown task number, which keeps it from a 5.

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

Conciseness3/5

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

It is compact but structured as one dense run-on sentence that opens with 'A task with...' instead of a verb, so the core action and payload enumeration compete with the reassigned/hand-off caveat. No wasted filler, but the front-loading could be much better.

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?

With a single required parameter, no output schema, and annotations covering the safety profile, the description does the needed work by enumerating the returned fields and flag semantics. Only edge-case behavior (invalid/unknown task, response size) is unaddressed.

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?

Schema coverage is 100% (the single parameter documents number-or-id with an example), so the baseline would be 3. The description adds genuine meaning beyond that: visibility scope ('any task you may see') and the note that pool tasks are resolvable by number if you have 'View all tasks'.

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 names the resource and the lookup key ('Finds any task you may see by its number'), and enumerates what the read returns (description, notes/comments, files, parent and subtasks, how_to_update). It is distinguishable from the mutating siblings, though it opens with a noun phrase rather than a verb, which slightly delays the purpose.

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?

There is one concrete conditional rule: if 'reassigned' is set, read the comments before working on the task. Otherwise the when-to-use case (read a task before mutating it) is only implied, and no alternatives such as list_my_tasks are named for discovery-oriented cases.

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