Skip to main content
Glama
Sign In
Task Queue MCP

Task Queue MCP

by devops-riku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Assign a task

assign_task

Assign a task to a workspace member by email, to yourself, or back to the Task Pool. Include a reason when reassigning or returning it.

Instructions

Assigns a task to a member of its workspace by email, to you ("me"), or back to the Task Pool ("none"). Needs Assign tasks, except handing back your own 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": {
      "task": "<task>",
      "assignee": "<assignee>"
    },
    "name": "assign_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task: its number, e.g. TASK-000123, or its id.
reasonNoWhy, when reassigning or handing it back.
assigneeYesAn email, "me", or "none".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false and openWorld=true, so the safety profile is covered. The description adds genuinely new behavioral context: an authorization prerequisite and the exception that handing back your own task needs no permission. It still omits side effects such as whether the previous assignee is notified.

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 tight sentences: the core action and assignee modes come first, and the permission caveat follows. There is no redundant restatement of the name or schema and nothing extraneous.

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 three-parameter mutation with no output schema, the definition covers the action, the accepted assignee forms, and the permission model. The remaining gap is what a successful call returns and how invalid assignees (non-members) are handled, which matters more here because no output schema exists.

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 are already documented in the schema, which sets the baseline at 3. The description adds modest value by clarifying that "none" returns the task to the Task Pool and that the email must belong to a member of the task's workspace — semantics the schema's one-line "An email, 'me', or 'none'" does not convey.

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 ("Assigns a task") and enumerates the three assignee modes: workspace member by email, "me", or "none" (Task Pool). It is clear what the tool does, though it never names or contrasts a sibling such as move_task, which an agent might confuse with reassignment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage condition — you need the "Assign tasks" permission, except when handing back your own task — which tells the agent when the call will succeed or fail. It does not explicitly route to alternatives (e.g. when to use update_task instead), so it stops short of full when/when-not guidance.

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