Skip to main content
Glama

krusch_task_status

Read-onlyIdempotent

Check the state of a staged two-phase-commit task to see whether it is staged, blocked by an invariant, applied, rejected, or aborted.

Instructions

Inspect the state of a staged 2PC task (STAGED, BLOCKED_INVARIANT, APPLIED, REJECTED, ABORTED).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "krusch_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds real value beyond that by naming the full outcome vocabulary (STAGED, BLOCKED_INVARIANT, APPLIED, REJECTED, ABORTED), which tells the agent what results to expect. It still omits behavior for unknown task_ids and not-found or error cases.

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

Conciseness5/5

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

A single sentence with the verb and resource front-loaded and the state enumeration kept in a compact parenthetical. No filler or restatement of the title.

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?

For a one-parameter read-only status tool with rich annotations and no output schema, this is close to sufficient: the agent knows what it inspects and what states can come back. The remaining gap is task_id format and error/empty behavior, which are minor for this complexity.

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?

One parameter (task_id) with 0% schema description coverage, so the description must carry the burden. Saying the target is a "staged 2PC task" implies task_id identifies such a task, but it says nothing about expected format, whether it is a route/run identifier, or what happens for unknown IDs.

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?

Specific verb ("inspect") plus a specific resource ("state of a staged 2PC task") and it enumerates the possible states. It is clearly a read-only status check, not a mutation like krusch_apply_diff or krusch_abort. It does not explicitly distinguish itself from similarly-named siblings such as krusch_stack_status or get_workspace_status, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the state list suggests you call this after staging a task to see whether it is STAGED, BLOCKED_INVARIANT, APPLIED, etc. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling for a different kind of status check.

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