Skip to main content
Glama

misakanet_preflight

Read-onlyIdempotent

Check risk level before executing high-risk operations. Matches your intent against lesson triggers and risk profiles to warn you before RAG builds, WSL/GPU tasks, or bulk imports.

Instructions

Check risk level before executing high-risk operations. Matches agent intent against lesson triggers and risk profiles to provide proactive warnings before you start. Use before RAG builds, WSL/GPU tasks, bulk imports, or any operation that might fail.

Choosing among the three retrieval tools: no error yet and a task about to start → memory_context; an actual error or keyword in hand → search; something risky about to run and no error yet → preflight. Not for: retrieving lessons (that is search or memory_context) — the return value is a risk verdict and guards, not lesson content. Input semantics: intent (required) describes what you plan to do in concrete terms (e.g. 'build RAG pipeline with ChromaDB'); context (optional) describes the environment (e.g. 'WSL, GPU 8GB'). Output schema: JSON with {risk_level (low|medium|high), intent, matched_lessons: [{id, title, domain, relevance}], guards: [string]}. Matched lessons are pulled from the local corpus using keyword overlap — a high risk_level with empty matched_lessons means the profile matched (e.g. 'GPU' triggers the WSL profile) but no specific lesson was close enough. That reading holds only while index_status is "ok"; it is "unreadable" when data/lessons.json could not be read or parsed, and then matched_lessons is empty because no lesson was checked rather than because none matched, with index_error saying why. Guards are concrete 'do X before Y' suggestions drawn from matched profiles and lessons. Error cases: missing intent returns {error}. Side effects: none — this is a read-only check. Auth: none. Rate limits: local stdio process only.

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

NameRequiredDescriptionDefault
intentYesTask intent description (e.g. 'build RAG index from PDFs')
contextNoEnvironment context (e.g. 'WSL, GPU 8GB')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.17.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations by stating auth is not required, that it runs as a local stdio process, and how matching actually works (keyword overlap against the local corpus). It also discloses two degraded states — high risk_level with empty matched_lessons, and index_status 'unreadable' — that an agent would otherwise misread as 'nothing matched'.

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 purpose, then the routing rule, then exclusions, then outputs and failure modes — a sensible order. It is dense and long, and the 'Side effects: none' line partly duplicates readOnlyHint, but almost every remaining sentence carries information.

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?

There is no output schema, and the description compensates by spelling out the return shape (risk_level, matched_lessons, guards, index_status, index_error) and the error case for missing intent. For a two-parameter advisory tool, an agent has everything needed to call it and interpret the result.

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 the schema's own examples ('build RAG index from PDFs', 'WSL, GPU 8GB') are effectively repeated in the description, so added meaning is limited. The description does clarify the intent/context split and the missing-intent error case, but broadly the schema carries this dimension.

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 and resource — check risk level before executing a high-risk operation — and immediately distinguishes itself from siblings by naming memory_context and search as the retrieval alternatives. An agent can classify a request without opening any schema.

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 explicit when-to-use triggers ('before RAG builds, WSL/GPU tasks, bulk imports'), an explicit when-not-to-use line ('Not for: retrieving lessons'), and a decision rule over the three retrieval tools. Nothing is left to inference.

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