Skip to main content
Glama

task_delegate

Delegate a user task to another user while the original owner retains ownership; the delegate can complete it to support escalation workflows.

Instructions

Delegate a user task to another user. The original owner retains ownership but the delegated user can complete it. Use for escalation workflows.

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": {
      "id": "<id>"
    },
    "name": "task_delegate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose the non-obvious semantic that delegation preserves owner while allowing completion, but says nothing about the delegated user needing to be supplied, permission requirements, whether delegation is reversible, the resulting task state, or the response — meaningful gaps for a mutation tool.

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?

Three short sentences, front-loaded with the action and followed by the distinguishing semantics; no wasted wording, though the third sentence is thin enough that it could have been merged or expanded to include the missing parameter guidance.

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?

For a state-changing task operation with no annotations, no output schema, and an undocumented lone parameter, the description is not sufficient: the mechanism for identifying the delegate is missing, as is what the caller gets back and whether the action can be undone.

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?

The single parameter has 0% schema description coverage, and the description never explains that "id" is the task identifier. Worse, the text implies a target user must be provided ("delegate ... to another user") while the schema exposes no such field, leaving the agent unable to determine how the delegate is specified.

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 a specific verb and resource ("Delegate a user task") and distinguishes the operation from a plain reassignment by explaining that "the original owner retains ownership but the delegated user can complete it." It does not name a sibling such as task_setAssignee as the contrasting option, which keeps it short of a 5.

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?

"Use for escalation workflows" gives a context cue for when to reach for this tool, but there is no guidance on when NOT to use it and no mention of the obvious alternative (changing the assignee outright), so the agent must infer the boundary.

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