Skip to main content
Glama

krusch_explain

Read-onlyIdempotent

Explains why a task was staged or blocked by project invariants, showing the specific rule that stopped or allowed the change.

Instructions

Explain why a task was staged or blocked by project invariants.

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_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The description adds that the answer is framed around 'project invariants', which is genuine context, but it does not say what happens for an unknown or non-blocked task_id or what shape the explanation takes. Useful but not rich.

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?

One sentence with the key qualifier (staged or blocked, invariant-driven) front-loaded and no filler. It is efficient, though a clause on what the explanation contains would have earned its space.

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 diagnostic tool with no output schema and a low-complexity surface, the description covers the essential who/what. The remaining omissions (output contents, edge-case behavior) are modest given the tool's simplicity.

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?

There is a single required parameter, task_id, with 0% schema description coverage, so the description is the only place semantics could be added. It implies the argument identifies the staged/blocked task but adds no format, source, or validity detail beyond the parameter name. With just one self-evident parameter this is a minor gap.

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?

States a specific verb ('Explain') and a specific subject ('why a task was staged or blocked by project invariants'), which is concrete enough for an agent to know it retrieves diagnostic reasoning rather than raw state. It does not name or differentiate against siblings such as krusch_task_status or krusch_stack_status, which is the only thing keeping it from a 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?

The condition 'staged or blocked' implies when to reach for this tool, but there is no explicit when-to-use/when-not-to-use statement and no pointer to alternatives for adjacent needs (e.g. checking status versus understanding the blocking invariant). Usage is inferable rather than instructed.

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