Skip to main content
Glama
kensaurus

Mushi-Mushi

by kensaurus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Move report between states

transition_status
DestructiveIdempotent

Move a report to a new workflow state, enforcing transition rules. Use to dismiss duplicates or mark fixed.

Instructions

Move a report to a new workflow state, enforcing the same transition rules as the admin UI. Valid targets: classified, grouped, fixing, fixed, verified, reopened, dismissed. When dismissing, closedReason (duplicate, not_reproducible, wont_fix, working_as_intended, spam) sets what the reporter is told — spam closes silently, and duplicate needs the report grouped under another one first; reporterMessage posts your note to the reporter verbatim. Returns { ok }. Write; idempotent (setting the current status is a no-op); rejects illegal transitions. Use to dismiss a duplicate or mark fixed; use merge_fix to mark fixed via a merged PR, or reopen_report for the reopened path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoReason for the transition (audit trail)
statusYesTarget status (resolved is stored as fixed)
reportIdYesReport UUID (`report_id` is accepted too.)
closedReasonNoWhen dismissing: what the reporter is told (spam closes silently)
reporterMessageNoOptional note posted to the reporter verbatim

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.13
    • addedInput schema / properties / closedReason
      Added value: +{
+  "description": "When dismissing: what the reporter is told (spam closes silently)",
+  "enum": [
+    "duplicate",
+    "not_reproducible",
+    "wont_fix",
+    "working_as_intended",
+    "spam"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / reporterMessage
      Added value: +{
+  "description": "Optional note posted to the reporter verbatim",
+  "maxLength": 10000,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.12
    • changedInput schema / properties / reportId / description
      Previous value: -"Report UUID"New value: +"Report UUID (`report_id` is accepted too.)"
  3. Changed1 schema field changedv0.1.10
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed2 schema fields changedv0.1.9
    • changedInput schema / properties / status / description
      Previous value: -"Target status"New value: +"Target status (resolved is stored as fixed)"
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "pending",
-  "classified",
-  "grouped",
-  "fixing",
-  "fixed",
-  "resolved",
-  "verified",
-  "reopened",
-  "dismissed"
-]New value: +[
+  "pending",
+  "classified",
+  "triaged",
+  "in_progress",
+  "grouped",
+  "fixing",
+  "fixed",
+  "resolved",
+  "verified",
+  "reopened",
+  "dismissed"
+]
  5. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare write/idempotent/destructive, but the description adds genuinely non-obvious behavior: illegal transitions are rejected, setting the current status is a no-op, spam closes silently, and a duplicate dismissal requires the report to be grouped first. It also discloses the return shape 'Returns { ok }'. Minor gap: it doesn't spell out permission requirements.

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?

Front-loaded with the core action and valid targets, then prerequisites, then the alternative routing. It is a dense single block, but essentially every clause earns its place; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-param mutation with no output schema, the description covers purpose, valid targets, side-effect semantics, preconditions, return value, and the sibling alternatives. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds the curated set of legal transition targets and the duplicate-grouping precondition on closedReason. Some of its semantics (verbatim reporter message, silent spam close) duplicate the schema, but the transition-target constraint and ordering prerequisite are net-new value.

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?

States a specific verb+resource ('Move a report to a new workflow state') and immediately scopes it with 'enforcing the same transition rules as the admin UI', which tells the agent this is a state-machine transition, not an arbitrary field update. It is clearly distinguishable from siblings like merge_fix and reopen_report, which it names.

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?

Explicitly routes the agent: 'Use to dismiss a duplicate or mark fixed; use merge_fix to mark fixed via a merged PR, or reopen_report for the reopened path.' Both the when-to-use and the alternatives with their selecting conditions are stated, leaving nothing 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