Skip to main content
Glama

task_resolve

Resolves a delegated task and returns ownership to the original owner after the delegate completes work, restoring normal task ownership.

Instructions

Resolve a delegated task, returning ownership to the original owner. Use after the delegate has completed their work to restore normal ownership.

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

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the key side effect (ownership transfer back to the original owner), which is the most important thing an agent needs. However, it omits preconditions (must the task actually be in a delegated state?), required permissions, error behavior for non-delegated tasks, and whether the operation is idempotent or reversible.

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 sentences, no filler, with the action and its effect stated first and the timing guidance second. Nothing is redundant or buried.

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 one-parameter mutation with no annotations and no output schema, the description covers purpose and timing but leaves gaps around preconditions, the `id` argument, and the response. It is minimally sufficient to attempt a call but not sufficient to call it correctly in edge cases.

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?

There is a single required parameter, `id`, and schema description coverage is 0%, so the description is the only place meaning could be added — yet it never mentions the parameter at all. The agent must infer that `id` is the task identifier, and nothing indicates whether it is the delegated-task id or some other reference.

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 gives a specific verb+resource ("Resolve a delegated task") plus the resulting state change ("returning ownership to the original owner"), which is more informative than the bare name. It implicitly contrasts with task_delegate and task_complete by scoping the action to already-delegated tasks, though it never names an alternative explicitly.

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?

"Use after the delegate has completed their work to restore normal ownership" is a clear trigger condition that tells the agent when this tool applies. It stops short of exclusions — e.g. whether to use task_resolve versus task_complete or task_setAssignee when the work is unfinished or the task was never delegated.

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