misakanet

by io.github.Ikalus1988

misakanet_preflight

Read-onlyIdempotent

[GUARD / RISK CHECK] Check risk level before executing high-risk operations. Matches agent intent against lesson triggers to provide proactive warnings. Use before RAG builds, WSL/GPU tasks, bulk imports, or any operation that might fail. Choosing among the retrieval tools: no error yet and a task about to start → misakanet_memory_context (stdio-only); an actual error or keyword in hand → misakanet_search; something risky about to run and no error yet → this one, which returns a risk verdict and guards, not lesson content. No side effects — safe to call multiple times before acting. Open, read-only: anonymous calls are rate-limited; misakanet_register lifts the limit. Returns: object {risk_level: 'low'|'medium'|'high', intent, matched_lessons: [{id, title, domain, relevance}], guards: [string]}. Example: misakanet_preflight(intent='build RAG pipeline with ChromaDB')

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": {
      "intent": "<intent>"
    },
    "name": "misakanet_preflight"
  }
}

Input Schema

Name	Required	Description	Default
`intent`	Yes	Required: what you plan to do (e.g. 'build RAG pipeline with ChromaDB').
`context`	No	Optional: additional context about the environment or setup.

Output Schema

Name	Required	Description	Default
`error`	No
`guards`	No
`intent`	No
`risk_level`	No
`matched_lessons`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'No side effects — safe to call multiple times' largely restates structured data. The genuinely additive details are the anonymous-call rate limit and that misakanet_register lifts it; without those the description would add little beyond the annotations.

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 guard tag and the core directive, then routing rules. It is dense and mostly earns its space, though the explicit 'Returns:' block duplicates the existing output schema and adds length.

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 low-parameter, read-only check tool the description covers purpose, routing, rate-limit behavior, and return shape. With annotations and an output schema already present, 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.

Parameters3/5

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

Schema coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The inline example intent='build RAG pipeline with ChromaDB' illustrates expected format and slightly enriches intent semantics, but no new constraints or interaction rules are offered.

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?

Opens with a bracketed role tag plus a specific verb+resource: 'Check risk level before executing high-risk operations', and clarifies it returns a risk verdict and guards rather than lesson content. This cleanly separates it from misakanet_search and misakanet_memory_context even though the latter isn't in the sibling list.

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?

Gives an explicit routing rule with three named conditions: no error and task about to start → memory_context, actual error/keyword in hand → search, something risky about to run with no error yet → this tool. It also enumerates trigger scenarios (RAG builds, WSL/GPU tasks, bulk imports).

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

All misakanet tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.