Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_task_context

Read-onlyIdempotent

Fetch all necessary context for a task—associated items, flows, files, functions, and optional interactions and notes—to resume work from a single call.

Instructions

Get complete context for resuming work on a specific task/subtask/sidequest. Single call retrieves item + associated items + flows + files + functions + optionally interactions and notes. Uses cached project root internally.

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_idYesID of the task/subtask/sidequest
task_typeNoType of task: 'task', 'subtask', 'sidequest'. Auto-detected from task_id if omitted.
include_interactionsNoInclude function dependency interactions
include_historyNoInclude note history for task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds value by noting it 'uses cached project root internally' and that retrieval is optional for some components. No contradictions.

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?

Two sentences, front-loaded with the core purpose. No extraneous words; every sentence provides essential information.

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?

Comprehensive for a tool with no output schema: lists all retrieved data types. Could benefit from brief mention of return structure, but given sibling complexity and annotations, this is adequate.

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%, and the description mentions auto-detection of task_type and optional includes. However, it does not add significant meaning beyond the schema descriptions themselves.

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 description clearly states it retrieves 'complete context for resuming work on a specific task/subtask/sidequest' and lists all components returned (item, associated items, flows, files, functions, optionally interactions and notes). This distinguishes it from more specific sibling tools.

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 description implies use when full context is needed but provides no explicit guidance on when to use alternatives (e.g., get_task_files, get_task_flows). It mentions it's a 'single call' but does not contrast with other tools.

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

Deploy Server

Other Tools