Retrieve a task's closure schedule and last status to determine if it is actually closed or just context-ready.
Get a task's persisted closure schedule and last observed status. context_ready means the daemon read its status, NOT that the task was closed.
| Name | Required | Description | Default |
|---|---|---|---|
| task_key | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.3.0Output schema / properties / result / anyOfPrevious value: -[
- {
- "properties": {
- "checked_at": {
- "anyOf": [
- {
- "format": "date-time",
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null
- },
- "close_at": {
- "format": "date-time",
- "type": "string"
- },
- "current_status": {
- "anyOf": [
- {
- "additionalProperties": true,
- "properties": {
- "category": {
- "anyOf": [
- {
- "additionalProperties": true,
- "properties": {
- "id": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "name"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null
- },
- "id": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "name"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null
- },
- "revision": {
- "default": 1,
- "type": "integer"
- },
- "state": {
- "default": "pending",
- "enum": [
- "pending",
- "context_ready"
- ],
- "type": "string"
- },
- "target_status": {
- "minLength": 1,
- "type": "string"
- },
- "task_key": {
- "type": "string"
- }
- },
- "required": [
- "task_key",
- "close_at",
- "target_status"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "properties": {
+ "checked_at": {
+ "anyOf": [
+ {
+ "format": "date-time",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "close_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "current_status": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "properties": {
+ "category": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "revision": {
+ "default": 1,
+ "type": "integer"
+ },
+ "state": {
+ "default": "pending",
+ "enum": [
+ "pending",
+ "context_ready",
+ "waiting",
+ "completed",
+ "cancelled",
+ "suspended"
+ ],
+ "type": "string"
+ },
+ "target_status": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "task_key": {
+ "type": "string"
+ },
+ "workflow_fingerprint": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "workflow_id": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "workflow_revision": {
+ "anyOf": [
+ {
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ }
+ },
+ "required": [
+ "task_key",
+ "close_at",
+ "target_status"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description adds a key behavioral detail: context_ready means the daemon read the status, not that the task was closed. This goes beyond annotations without contradicting them, providing valuable context for interpreting results.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy, front-loading the core purpose and then adding a crucial clarification. Every word contributes to the tool's understanding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter) and the presence of an output schema, the description covers the essential purpose and the critical nuance about context_ready. It is sufficiently complete for an agent to invoke correctly, though it could potentially mention that it returns only closure-related data, which is implied.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has a single required parameter, task_key, with no description, and schema description coverage is 0%. The description does not explain what task_key represents or its format, relying entirely on the parameter name. Since the schema lacks detail, the description should have compensated but did not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a task's persisted closure schedule and last observed status, using specific verbs and a distinct resource. It also distinguishes itself from sibling tools like teamstorm_get_task by focusing on closure-specific data, and the clarification about context_ready adds precision.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool (when closure schedule/status is needed) and provides an important usage note that context_ready does not mean the task is closed. However, it does not explicitly name alternative tools or state when not to use it, though the context is reasonably clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.