Skip to main content
Glama

task_get

Read-onlyIdempotent

Retrieves task details—original goals, rules, lease owner, progress, and recovery status—to resume a project; set include_details to export the full record.

Instructions

Resume a project with original goals, rules, current lease owner and compact progress. executor identifies its owner without sharing write tokens; active_background identifies ongoing automatic recovery even while it awaits queued work. Follow operation_get before starting a competing repair. Use task_records for paged history. include_details=True returns the complete record for export.

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_id": "<task_id>"
    },
    "name": "task_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
include_detailsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered and the description correctly does not contradict it. What it adds is semantic context about returned fields (executor, active_background, lease owner) rather than behavior such as permission requirements or staleness guarantees. Because an output schema exists, restating return fields earns only modest extra credit.

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?

Four sentences with little filler, but the front-loaded opening is the least clear part, burying the actual fetch semantics behind a confusing "Resume a project" framing. Usage pointers (operation_get, task_records) and the include_details note are well placed; the executor/active_background sentence is dense but earns its space.

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 an output schema present, the description need not explain return values, and it still sketches the important ones plus a prerequisite and an alternative tool. The main residual gap is task_id semantics and error behavior, which matters little for a two-parameter read.

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 0% for the two parameters, so the description must carry the load. It explains include_details=True as "returns the complete record for export" but says nothing about task_id format, whether an unknown id errors or returns empty, or the default compact behavior beyond implication. Half the parameters remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Resume a project with original goals, rules, current lease owner and compact progress" describes the payload rather than stating plainly that the tool fetches a task record by task_id. The resource is inferable (task/project state) but the leading verb "Resume" reads like an action, which muddies a read-only fetch. Sibling differentiation is present only via the task_records and operation_get pointers, not in the core purpose statement.

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?

It gives two concrete routing rules: "Follow operation_get before starting a competing repair" and "Use task_records for paged history," which tells an agent both a prerequisite check and an alternative for a different need. It does not address when to prefer task_get over task_list or task_claim, so the coverage is clear but not exhaustive.

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