Skip to main content
Glama
ihorponom

agentpack

by ihorponom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_status

Read-only

Print a compact current-task state line for an AI coding session, or pass an id to inspect one task's objective, constraints and next actions. Read-only.

Instructions

Print a compact current-task state line by default; pass full: true for the detailed current view, or id to inspect a selected Passport with objective, constraints, all next actions and verification without switching tasks. Gate warnings always concern the actual current task. No source-cache scan; use task_audit for the full continuity audit. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTask Passport id to inspect in full without changing the current task or lifecycle.
fullNoShow the detailed current-task summary instead of the compact state line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / full
      Added value: +{
+  "description": "Show the detailed current-task summary instead of the compact state line.",
+  "type": "boolean"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Task Passport id to inspect without changing the current task or lifecycle. Omit for the legacy current-task summary."New value: +"Task Passport id to inspect in full without changing the current task or lifecycle."
  2. Changed1 schema field changedv1.6.8
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Task Passport id to inspect without changing the current task or lifecycle. Omit for the legacy current-task summary.",
+  "minLength": 1,
+  "type": "string"
+}
  3. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the 'Read-only' clause is partly redundant. The description still adds real behavioral context: gate warnings always pertain to the actual current task even when inspecting another id, and no source-cache scan occurs. It does not disclose pagination or output volume, which is a minor gap.

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?

Default behavior is front-loaded in the first clause, then the two deviations from default. The single dense sentence is efficient, though the 'Gate warnings' aside is slightly intrusive to the flow.

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 carries the return-value burden and does so reasonably: a compact state line by default, and objective, constraints, next actions, and verification in the id/full view. It is complete enough to call correctly, though it never mentions lifecycle side effects beyond asserting none.

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 description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description restates the roles of id and full without adding format, syntax, or edge-case detail beyond the schema's own wording.

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 states a concrete verb and resource ('Print a compact current-task state line') and enumerates the three operating modes (default, full: true, id). It explicitly distinguishes itself from the sibling task_audit, so an agent can separate the two without opening schemas.

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?

It names the default behavior and the conditions that select each alternative ('pass full: true for the detailed current view, or id to inspect a selected Passport'), and it routes the full continuity audit to task_audit explicitly. Nothing about mode selection is left to inference.

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