Skip to main content
Glama

get_delegated_task_updates

Check where a delegated task stands: its current state, peer messages since your last update, and outputs so far. Optionally wait for new activity after a given version.

Instructions

Where a task you delegated stands: its state, everything the peer said since your last message to it, and its outputs so far. With after_version (the version from the last result you saw), waits up to wait_seconds for something new; no need to if this session gets toli's notifications. For the whole conversation, use get_task_full.

Input Schema

NameRequiredDescriptionDefault
task_idYes
wait_secondsNowith after_version, how long to wait (default 60, max 120)
after_versionNothe version from the last update you saw: wait until the task is newer

Output Schema

NameRequiredDescriptionDefault
peerYes
stateYes
task_idYes
versionYespass as after_version to wait for the next change
deadlineYes
messagesYeseverything the peer said since your last message to it, oldest first: progress notes, its open question, its final answer
artifactsNothe task's outputs so far
session_idNo
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Since there are no annotations, the description must carry the full burden. It successfully discloses key behavioral traits: the specific content returned (state, messages, outputs), and the waiting behavior enabled by combining the wait_seconds and after_version parameters. This adds significant contextual depth beyond the input schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is effective but slightly conversational. While dense with information, the structure places the critical scope definition (updates on delegated tasks) first, followed by technical use cases and finally the sibling routing advice.

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?

Given the existence of an output schema, the description doesn't need to explain return structure. It provides all necessary context for an agent to understand the tool's scope (delegated tasks), its monitoring capability (wait_seconds/after_version), and its relationship to other tools (get_task_full).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is only 67%, the description clearly explains the semantics of the optional parameters. It describes the interdependent nature of wait_seconds and after_version, explaining that the waiting mechanism is triggered by using a specific version identifier, which adds practical meaning to the parameters.

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 defines the tool as the place to check the status of a delegated task. It differentiates itself by focusing on task 'updates' (state, peer messages, outputs) rather than providing the full task details, and it explicitly refers to get_task_full as the alternative for the whole conversation.

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 usage guidelines are exceptionally clear: it advises against relying on the tool for long-term monitoring ('no need to if this session gets toli's notifications') and explicitly directs the agent to use the 'get_task_full' sibling tool when broad conversation context is required. This preemptive guidance prevents misapplication.

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