Skip to main content
Glama

get_task

Fetch full task context—description, relations, and last five comments—or return one attachment's text by file ID.

Instructions

Full tasks: description, relations, the last 5 comments. file= returns one attachment's text instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
fileNoattachment id
commentsNoevery comment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the returned field set and that comments are truncated to the last 5, plus the alternate attachment-text return for `file=`. It does not say what happens when `ids` is empty (does it return everything?), how `comments=true` interacts with the 5-comment default, or what an invalid attachment id yields.

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?

Two short sentences with no filler, and the primary payload is stated before the mode exception. The clipped 'Full tasks:' fragment trades grammar for brevity without losing meaning, though a slightly fuller opening would cost nothing.

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?

With no output schema and no annotations, the description does part of the job by enumerating returned fields. But for a 3-parameter read tool with an unexplained `ids` parameter and no statement of empty-input behavior, an agent could still call it incorrectly (e.g., omitting ids expecting a task list).

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 67%. The description adds meaning for `file` (returns attachment text instead of task data) and implies a default/override relationship for `comments`, but it never mentions the `ids` parameter at all, which is the primary selector. The tension between the schema's 'every comment' and the description's 'last 5 comments' is left unresolved.

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 (tasks) and enumerates the payload it returns — description, relations, last 5 comments — so an agent knows this is a detailed retrieval rather than a list. The `file=` clause states a second, clearly different mode (attachment text instead of task data). It is telegraphic ('Full tasks:') rather than verb-led, but the purpose is unambiguous.

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?

The `file=` sentence gives real guidance for choosing between the two modes of this tool. However, there is nothing about when to call this versus list_tasks (to discover ids) or save_task, and no stated prerequisites such as needing an existing task id. Usage is implied rather than instructed.

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