Skip to main content
Glama

Get a task

taskhold_get
Read-only

Get one task in full: status, priority, project, labels, repeat, time worked and waited on the person, description, numbered steps with ids and summaries, the 10 latest notes, the completion summary and what changed (files, checks, links, risks, how to verify). Unknown ids fail with "Task not found".

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": "taskhold_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the description is free to add real value: it discloses exactly what is returned (including capped "10 latest notes") and the error semantics for unknown ids ("Task not found"). It doesn't mention pagination or rate limits, but the return and error disclosure is meaningful beyond the annotations.

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?

Front-loaded with the verb and scope, then a compact field enumeration. The long clause is dense but every listed item describes a return field, which has no output schema to carry it, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the job of describing return contents and does so thoroughly, plus error behavior. For a one-param read-only tool, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so task_id is already documented; the description adds only that it is an id resolving to one task and that unknown ids fail, which is marginal beyond the schema. Baseline 3 applies when the schema carries parameter meaning.

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+resource ("Get one task in full") and enumerates the returned fields, making the retrieval scope concrete. It does not explicitly name siblings like taskhold_get_summary or taskhold_list to distinguish when this differs, so it falls short of the top band.

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?

Implicit usage is clear (fetch a single task by id), and the "not found" behavior is noted, but there is no explicit when-to-use guidance or comparison against alternatives such as get_current, get_summary, list, or search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources