Skip to main content
Glama

get_task_context

Read-onlyIdempotent

Retrieves complete details for a single task—including comments, artifacts, dependencies, and activity—in one consolidated call, eliminating multiple separate queries.

Instructions

Get EVERYTHING about ONE TASK in a single call: full details + comments + artifacts + dependencies + activity. Combines the results of get_task, list_comments and list_artifacts for one task in a single response.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID (full UUID or 6–12 char hex short-ID prefix).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

While annotations cover safety (readOnlyHint=true), the description adds crucial behavioral context by enumerating exactly what data streams are integrated (details, comments, artifacts, dependencies, activity). This helps the agent understand the scope of the returned data packet.

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?

The description is highly efficient, using two sentences. The first sentence is a powerful summary, and the second provides the technical justification (combining results) without unnecessary filler.

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?

Given the complexity of aggregating multiple data sources, the description is perfectly complete. It defines the scope of the output contents and the mechanism of the call (single response), which is more valuable than detailing the output structure.

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?

The schema coverage is 100%, meaning the schema already defines the parameter fully. The description provides no new semantic meaning to 'task_id' beyond the context of a single task ID.

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

Purpose5/5

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

The purpose is stated clearly using a specific verb ('Get') applied to a resource ('ONE TASK'). It immediately distinguishes itself by explaining that it provides a comprehensive overview ('EVERYTHING') that combines data from multiple underlying tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool provides explicit guidance on its usage pattern: it should be used when the user needs a holistic view of a task, as it explicitly 'Combines the results of get_task, list_comments and list_artifacts' into a single call, implying efficiency over multiple separate calls.

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