Skip to main content
Glama

task_get

Retrieve complete details for a single Taskwarrior task, including claim, handoff, context, dependencies, and the last five notes.

Instructions

Full detail of one task: claim, handoff, context, dependencies, last 5 notes.

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

Input Schema

NameRequiredDescriptionDefault
idYesTask id: the 8-character id shown in task_context/task_list (full UUID also works).
cwdNoSession folder (absolute path). Filled in by the OpenCode plugin; other clients pass the working folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral value by disclosing the returned sections and implicitly a truncation limit ('last 5 notes'), which tells the agent notes are capped. It says nothing about behavior for a missing/invalid id, whether the call is side-effect free, or what 'handoff' and 'claim' look like when unset.

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?

A single compact line with zero filler, front-loading the resource and then listing the payload sections. Nothing could be removed without losing information.

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 two-parameter read tool with no output schema, the description usefully stands in for a return-value contract by enumerating the sections returned. The main remaining gap is failure/empty-state behavior, which is minor for a simple getter.

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 both parameters (id, cwd) are already documented in the schema, including the 8-character id form. The description adds no additional meaning about either parameter, which is acceptable at full schema coverage but earns no bonus.

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 (a single task) and enumerates exactly what the response contains: claim, handoff, context, dependencies, last 5 notes. That distinguishes it reasonably well from task_list (plural listing). It stops short of a clean distinguishing sentence versus task_context, which by name could also return task context.

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?

Usage is only implied: 'Full detail of one task' suggests calling it when you need a single task's complete record rather than a list. There is no explicit when-to-use statement, no mention of when to prefer task_list or task_context, and no stated prerequisites.

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