MisakaNet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| misakanet_searchA | Search MisakaNet's public failure-lesson index by error text, keyword, or topic. Use when you need to discover relevant lessons and do not already know a lesson ID. Input semantics: query is required; domain optionally filters by lesson domain; top limits ranked results and defaults to 5. kind filters by result type: 'lessons' (lesson files only), 'evidence' (results with evidence_refs or verification), 'related' (cross-referenced/tag-overlap), 'all' (default). kind is auto-detected from query intent when omitted (e.g. 'lesson about X' → lessons, 'evidence for X' → evidence). Set explain=true to return matched terms, TF-IDF, entity matches, vector similarity, and hybrid score components. detail controls progressive disclosure: compact (default, ~80 tok/lesson) for broad scans, summary (~200 tok) with domain/tags/fix, full for complete lesson markdown. Output schema: JSON with results[] and source; each result is a ranked lesson summary. Error cases: missing query, unavailable search index, or no matches (empty results). Side effects: none. Auth: none. Rate limits: local stdio process only; callers should keep result counts small. Do not use for private log collection; search only with redacted snippets. Use misakanet_get_lesson for full content. |
| misakanet_get_lessonA | Fetch one public MisakaNet lesson by repository path or lesson ID. Use after misakanet_search returns a promising result, or when a lesson is explicitly referenced; do not use it for broad discovery. Input semantics: provide either path or id. Output schema: JSON with path and markdown content, truncated to 5000 characters for MCP context. Error cases: missing path/id or lesson not found. Side effects: none. Auth: none. Rate limits: local stdio process only; fetch one lesson per call when possible. |
| misakanet_submit_usageA | [Experimental] Record that a public lesson helped with a problem. Use only after the user or calling agent explicitly chooses to submit usage feedback for a specific lesson. Input semantics: lesson_id is required; tool names the calling client; outcome should be solved, partial, not-helpful, or another short status. Output schema: JSON with lesson_id, tool, outcome, and status. Error cases: missing lesson_id. Side effects: currently returns a local placeholder report only. Auth: none. Rate limits: local stdio process only. |
| misakanet_submit_intakeA | Submit a failure-case intake when no matching lesson exists or a lesson was stale/incorrect. Use after misakanet_search fails to find a good match, or when the user resolved a problem not yet documented. Input semantics: problem is required (short description of the failure); kind defaults to missing_lesson; error, what_tried, fix, verification, and matched_lesson_id are optional. Output schema: JSON with submitted (boolean), intake_id, status (pending_review), redactions_applied, quality_score, and receipt. Error cases: missing problem, duplicate submission. Side effects: writes to data/contribution_queue.jsonl. Auth: none. Rate limits: local stdio process only. |
| misakanet_write_lessonA | Submit a complete, structured failure lesson. Use after resolving a problem and documenting the full failure→root cause→fix→verification chain. Requires a registered agent token (not anonymous). Input semantics: title, domain, problem, root_cause, fix (all required); verification, tags, token, source (optional). Output schema: JSON with lesson_id, status (pending_review), quality_score, quality_notes, redactions_applied, and receipt. Error cases: missing required fields, anonymous token, quality score below 75 threshold, duplicate submission. Side effects: writes to data/contribution_queue.jsonl. Auth: registered agent token required. Rate limits: local stdio process only. |
| misakanet_preflightA | 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. Input semantics: intent (required), context (optional). Output schema: JSON with risk level, matched lessons, and guards. Error cases: missing intent. Side effects: none. Auth: none. Rate limits: local stdio process only. |
| misakanet_usage_statusA | Check current usage status and remaining quota. Use to see how many free lesson reads remain and how many credits are available. Input semantics: user is optional (defaults to anonymous). Output schema: JSON with user, free_reads_used, free_reads_limit, free_reads_remaining, credits, is_registered, and next steps. Error cases: none. Side effects: none. Auth: none. Rate limits: none. |
| misakanet_registerA | Register an agent and receive a node_id and token for unlimited remote MCP access. Reading needs no registration; only write tools do. Local stdio MCP is unlimited and does not need registration. For remote HTTP MCP, call this tool first to get a token, then pass it as the user parameter in subsequent calls. Input semantics: agent_type is optional (defaults to 'unknown'); client_id is an optional stable identifier you generate once — with it, later calls return the same node_id and token and renew them, without it each call mints a new node. Output schema: JSON with node_id, token, registered_at, agent_type, and reused=true when an existing node was found for client_id. Error cases: invalid_client_id. Side effects: persists registration record. Auth: none. Rate limits: one registration per session. |
| misakanet_memory_contextA | Proactive half of the pair: call this BEFORE starting a task so failure-memory is in context from the first step; call misakanet_search once a specific error has actually appeared. How |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_lesson | Search MisakaNet for lessons matching an error or topic |
| triage_failure | Structured failure triage — find root cause and matching rescue cards |
| release_audit | Check release readiness against MisakaNet quality gates |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Lessons Index | Browse all published lessons (core + contrib) with metadata |
| Protocol Overview | failure-memory protocol configuration (trust tiers, rings, scoring) |
| README | Project overview, quickstart, and integration guide |
| Troubleshooting FAQ | Common issues and solutions for MisakaNet users |
| Changelog | Latest release notes and version history |
| Lesson by ID | Full lesson content and metadata by lesson ID |
| Domain List | List all knowledge domains with lesson counts |
TDQS
Scored across 9 tools
Several tools have overlapping retrieval purposes: misakanet_memory_context, misakanet_preflight, and misakanet_search all match text against the lesson corpus, with the proactive pair (memory_context vs preflight) differing mainly in task-start context vs risk-check emphasis. Similarly, misakanet_submit_intake and misakanet_write_lesson both write to the contribution queue, distinguished only by completeness. The long descriptions help, but an agent could still easily pick the wrong tool.
All tools share the misakanet_ prefix and snake_case, with most using a verb_noun pattern (get_lesson, search, submit_intake, register). Two names deviate: memory_context and usage_status are noun phrases rather than imperatives, creating a minor inconsistency. Overall the convention is predictable and readable.
Nine tools cover the domain well: retrieval (search, get_lesson), proactive context (memory_context, preflight), contribution (submit_intake, write_lesson), usage feedback, registration, and quota checking. The size feels appropriate for a failure-lesson server — neither thin nor bloated.
The core lifecycle is covered: discover lessons, fetch details, get proactive warnings, submit missing lessons/intakes, and manage registration/quota. The main gap is that the search tool references a closed vocabulary of domains from data/domains.json but provides no way to list those domains, which could leave agents guessing. No update/delete for lessons exists, but that is likely admin-side functionality.