Mushi-Mushi

What should I work on now?

triage_next_steps

Read-onlyIdempotent

Get a prioritized action list for triage: unblock blocked auto-fixes, merge in-flight fixes, address severe user reports, then cover routine chores. Use for 'what needs my attention'.

Instructions

Prioritised "do this next" list for the project: blocked auto-fixes first (with the unblock action), then in-flight fixes to shepherd to merge, then user-felt classified reports by severity, with robot/cron chores (dependency bumps) last. Returns { steps: [{ priority, action, reason, tool, args }], summary }. Read-only. Call this first when the user asks "what needs my attention / what should I triage or fix".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	No	Project UUID (defaults to the configured project). (`project_id` is accepted too.)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`steps`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.12Sep 24, 2026

addedInput schema / properties / projectId

Added value: +{
+  "description": "Project UUID (defaults to the configured project). (`project_id` is accepted too.)",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

removedInput schema / properties / project_id

Removed value: -{
-  "description": "Project UUID (defaults to the configured project).",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}

Changed2 schema fields changedv0.1.10Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Addedv0.1.9Aug 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and open-world, and the description reinforces read-only while adding real behavioral context: the priority ordering, the output shape, and the fact that next-step actions carry tool/args. It could note that it only recommends actions rather than executing them, but the read-only hint implies this.

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?

Two sentences carry a lot of useful detail without redundant fluff, and the most important 'prioritised next list' concept is front-loaded. The priority categories are packed into a long first sentence, but it remains readable and each clause earns its place.

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 an entry-point planning tool, the description covers the priority algorithm, output schema, read-only safety, and the exact user query that should trigger it. With an output schema present and annotations covering safety/idempotency, nothing essential for correct invocation appears 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?

The single optional projectId parameter is fully documented in the schema (100% coverage), including the default behavior and project_id alias. The description adds no additional parameter-level meaning, so the baseline 3 is appropriate.

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 specifies a clearly scoped verb-object: it returns a prioritised 'do this next' list for the project, with a defined ordering across blocked auto-fixes, in-flight fixes, reports, and chores. The trigger phrase 'Call this first when the user asks...' distinguishes it from siblings like triage_issue or get_recent_reports.

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

Usage Guidelines4/5

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

It gives an explicit when-to-use instruction: call first when the user asks what needs attention or what to triage/fix. It does not explicitly name alternatives or list when-not-to-use conditions, so it stops short of a 5.

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