TaskBullet

Get delegated task

get_task

Read-onlyIdempotent

Retrieve current status, title, completion timestamp, and result notes for a delegated task. Check awaitingCustomerConfirm to decide whether to confirm, cancel, or reopen.

Instructions

Get the current status, title, completion timestamp, and full result notes for a specific delegated task. awaitingCustomerConfirm true means ask the human, then confirm_task, cancel_task, or reopen_task. amNote is the AM or VA note. deliverableLinks lists https links. Stop when status is completed, failed, or cancelled. Customer cancel is cancelled, not pending or in_progress, and it does not send the completion webhook.

Input Schema

Name	Required	Description	Default
`taskId`	Yes	The taskId returned by delegate_task.

Output Schema

Name	Required	Description
`title`	No
`amNote`	No	AM or VA note.
`result`	No	Full VA result when completed. Never invent this.
`status`	No	Stop polling on completed, failed, or cancelled.
`taskId`	No
`priority`	No
`createdAt`	No
`completedAt`	No
`autoConfirmNote`	No
`deliverableLinks`	No	https links from the note.
`awaitingCustomerConfirm`	No	True means ask the human, then confirm_task, cancel_task, or reopen_task.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.0Oct 22, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "amNote": {
+      "description": "AM or VA note.",
+      "type": "string"
+    },
+    "autoConfirmNote": {
+      "type": "string"
+    },
+    "awaitingCustomerConfirm": {
+      "description": "True means ask the human, then confirm_task, cancel_task, or reopen_task.",
+      "type": "boolean"
+    },
+    "completedAt": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "deliverableLinks": {
+      "description": "https links from the note.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "priority": {
+      "type": "string"
+    },
+    "result": {
+      "description": "Full VA result when completed. Never invent this.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Stop polling on completed, failed, or cancelled.",
+      "type": "string"
+    },
+    "taskId": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.1Oct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, but the description adds non-obvious behavior: a customer cancel lands as 'cancelled' rather than pending/in_progress and does not fire the completion webhook. Those are side effects an agent could not infer from the annotations or schema. It stops short of covering rate limits or response shape beyond the listed fields.

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?

Front-loads the returned data and then layers the interpretation rules (awaitingCustomerConfirm, amNote, deliverableLinks, terminal statuses, cancel semantics) in short, terse sentences. A couple of the field glosses ('amNote is the AM or VA note') are near-redundant given the output schema, but overall every sentence carries usable information.

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?

For a single-parameter read tool with an output schema and full annotation coverage, this description supplies everything an agent needs: what is returned, how to read key fields, what to do on awaitingCustomerConfirm, when to stop, and the webhook quirk for customer cancels. Nothing material is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage ('The taskId returned by delegate_task'). The description adds no extra syntax, format, or sourcing guidance for taskId beyond what the schema says, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('Get the current status, title, completion timestamp, and full result notes for a specific delegated task') and enumerates the returned fields, so it is immediately distinguishable from list_tasks or get_call. The scope is a single task identified by taskId, and that is stated plainly.

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?

Gives explicit routing: when awaitingCustomerConfirm is true, ask the human and then call confirm_task, cancel_task, or reopen_task, naming the sibling tools by name. It also states the stopping condition (status completed, failed, or cancelled), so the agent knows when not to keep polling.

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

Deploy Server