Skip to main content
Glama

Get the person's updates

taskhold_updates
Read-only

What the person changed since you last looked: replies (notes), new tasks, priority changes, unblocks. Call when you resume, between steps, and after blocking (with wait, until the reply lands). Pass the last cursor you got (from any call) as since. Your own changes are hidden unless include_agent is true. Returns one line per change, oldest first (time, who, task, what, task id), then the next cursor, also when nothing is new. An unknown project returns no changes; an unknown task_id fails with "Task not found".

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

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for a change when there is none yet (0-50). Use after taskhold_block.
sinceNoCursor from the previous call. Omit the first time (you get the latest 20).
projectNoProject name, e.g. the repo folder ("api-server"). Any case, or an id. Unknown names match nothing.
task_idNoOnly changes to this task and its steps (e.g. the one you blocked)
include_agentNoAlso include changes made by agents, yours included (default: the person's changes only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Project name, e.g. the repo folder (\"api-server\"). Matched case-insensitively (or a project id). An unknown name matches nothing."New value: +"Project name, e.g. the repo folder (\"api-server\"). Any case, or an id. Unknown names match nothing."
  2. Changed1 schema field changed
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real operational context beyond that: your own changes are hidden unless include_agent is true, output is one line per change oldest-first, a cursor is returned even when nothing is new, an unknown project silently yields no changes while an unknown task_id raises 'Task not found'. The wait-until-reply pattern is also disclosed, though pagination limits and truncation behavior on large result sets are not.

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?

It is front-loaded with the purpose, then call timing, then cursor handling, then return shape and edge cases — every sentence carries distinct information with no filler. It is dense and slightly packed in the final sentence, but nothing is redundant.

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?

With no output schema, the description correctly takes on the return-format burden: line shape (time, who, task, what, task id) plus cursor, and the empty-result case. Combined with the error semantics and cursor convention, an agent has enough to call it correctly; only volume/limit behavior for the initial no-cursor call is left unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by clarifying that 'since' should be the cursor from any prior call (not just this tool's) and by tying 'wait' to the post-block resume flow. The remaining parameters are left to the schema, which already documents them well.

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 opens with a specific resource: a delta feed of 'what the person changed since you last looked', enumerating change types (replies, new tasks, priority changes, unblocks). That is clearly a change-feed tool rather than a single-record fetch, which separates it in spirit from taskhold_get/taskhold_progress, but no sibling is named, so the distinction is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives concrete call sites: 'when you resume, between steps, and after blocking (with wait, until the reply lands)', which tells an agent exactly when this tool is the right move. It stops short of naming an alternative (e.g., use taskhold_get for one task's current state) or stating when not to call it, so it stays a strong 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources