Skip to main content
Glama
Sign In

Morrowkin

by com.morrowkin
OverviewDiscussionsAdmin

Start diagnostic workflow

morrowkin_start_diagnostic_attempt

Start a private diagnostic attempt. Set chain true for a linear workflow, or choose a branching root from the scenario catalogue with chain omitted. Repair choices then determine the next fault. Each call creates an attempt, so retain the returned ID.

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": {
      "game": "<game>",
      "scenario": "<scenario>"
    },
    "name": "morrowkin_start_diagnostic_attempt"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYes
chainNo
scenarioYesStarting scenario ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that every call creates a new, private attempt (non-idempotent), that repair choices drive the next fault, and that a returned ID must be retained. It leaves out failure modes, authorization needs, and whether attempts expire, so not a 5.

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?

Three sentences, front-loaded with the action, zero filler. The branching/linear rule and the ID-retention warning each earn their place and appear in priority order.

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

Completeness3/5

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

With no output schema and no annotations covering return semantics, the description should cover more: it mentions a returned ID but not the rest of the response, and it references a 'scenario catalogue' without naming a tool to browse it. The undocumented 'game' parameter is a real gap for a required field.

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 coverage is only 33%, so the description must compensate. It explains 'chain' well (true = linear, omitted = branching root), but the 'game' enum with its two modes is completely unaddressed in both schema and description, and 'scenario' still lacks any hint on how to obtain valid 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?

States a specific verb and resource ('Start a private diagnostic attempt') and implicitly separates itself from the read_/act_on_ siblings by describing creation rather than continuation. It does not explicitly name those siblings, so the differentiation is inferable rather than stated.

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?

Gives clear conditional guidance: set chain true for a linear workflow, or omit it and pick a branching root from the scenario catalogue. It also warns that each call creates a new attempt, which tells the agent not to re-invoke casually. Missing an explicit pointer to act_on_diagnostic_attempt as the follow-up step.

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

All Morrowkin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources