Skip to main content
Glama

get_task

Read-onlyIdempotent

Retrieve all details for a specific task—notes, assignees, deadlines, checklist item IDs, attachments, labels, completion status, comments, and optional change history—using its task ID.

Instructions

Everything about one task: full notes, assignees, deadline, checklist items (with ids), attachments, labels, completion, and its comments (+ change history if include_history=True).

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

Input Schema

NameRequiredDescriptionDefault
task_idYes
include_historyNo
include_commentsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that change history is conditional on include_history=True and that comments are bundled by default, which is useful, but it says nothing about failure behavior for a missing task or whether the payload is paginated/truncated.

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 dense sentence, front-loaded with the scope, that spends its words only on what the tool returns and the one flag that changes the payload. No filler or restatement of the name.

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?

An output schema exists so return values need no prose explanation, and annotations cover the safety profile; the description still adds the field inventory and the history flag. The remaining gap is the undocumented include_comments toggle and task_id expectations for a 3-parameter tool.

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%, so the description must carry the parameter burden. It explains include_history clearly and implies comments are returned by default, but never mentions the include_comments parameter by name (nor that it can be set false), and leaves task_id format entirely to inference.

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 ('Everything about one task') and enumerates exactly what the payload contains: notes, assignees, deadline, checklist items, attachments, labels, completion, comments. That enumeration also implicitly separates it from siblings like get_task_comments and get_task_history, though those are never named.

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 by the scope phrase 'Everything about one task' – the agent can infer this is the broad fetch and that narrower siblings exist for comments/history, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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