MisakaNet

misakanet_search

Read-onlyIdempotent

[RETRIEVAL / READ] Search MisakaNet's public failure-lesson index by error text, keyword, or topic. This is the primary read path — run it first when you hit an error, before deciding to submit anything. For a known lesson ID or path, prefer misakanet_get_lesson — it skips ranking and returns the full content. detail controls progressive disclosure: compact (default, ~80 tok/lesson) for broad scans, summary (~200 tok) adds domain/tags/fix, full returns complete lesson data. FAQ: results may also include answered questions (type="faq", issue_url + answer) — if a maintainer already answered the same question, the answer surfaces here. Returns: object {results: [{id, title, domain, tags, path, description, score}], source, detail, query}; on no match: {no_match: true, suggestion, intake}. Example: misakanet_search(query='pip install timeout', domain='python', top=3)

Input Schema

TableJSON Schema

Name	Required	Description
`top`	No	Maximum ranked results to return. Defaults to 5; keep small for MCP context and latency.
`kind`	No	Filter by kind: 'lessons' (lesson files only), 'evidence' (results with evidence_refs or verification), 'related' (cross-referenced/tag-overlap), 'all' (default). Auto-detected from query intent when omitted.
`query`	Yes	Required redacted error message, keyword, or topic (e.g. 'pip install timeout' or 'DCO sign-off failed').
`detail`	No	Progressive disclosure: compact (default, ~80 tok) includes id/title/problem/freshness; summary (~200 tok) adds domain/tags/fix; full returns complete lesson data with path.
`domain`	No	Optional domain filter such as devops, python, network, feishu, rag, fanuc, or mcp.
`bm25_weight`	No	Override BM25 keyword weight (0-1). Higher favors exact keyword match. Default: 0.65. All weights must sum to 1.0.
`baseline_weight`	No	Override baseline score weight (0-1). Higher favors proven/popular lessons. Default: 0.15.
`metadata_weight`	No	Override metadata bonus weight (0-1). Higher favors matching domain/tags. Default: 0.20.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`detail`	No
`intake`	No
`source`	No
`results`	No
`no_match`	No
`suggestion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / kind

Added value: +{
+  "description": "Filter by kind: 'lessons' (lesson files only), 'evidence' (results with evidence_refs or verification), 'related' (cross-referenced/tag-overlap), 'all' (default). Auto-detected from query intent when omitted.",
+  "enum": [
+    "all",
+    "lessons",
+    "evidence",
+    "related"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "detail": {
+      "type": "string"
+    },
+    "intake": {
+      "properties": {
+        "args": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "no_match": {
+      "type": "boolean"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "answer": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "domain": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "issue_url": {
+            "type": "string"
+          },
+          "path": {
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "suggestion": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds substantial behavioral context beyond that: progressive disclosure through detail levels, the exact return object shape, the no-match fallback with suggestion and intake, and FAQ results surfacing. This richly describes what the agent should expect from the call.

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?

The description is front-loaded with the core purpose and primary-use directive, then moves logically through alternatives, detail behavior, FAQ caveat, return shape, and a practical example. Every sentence earns its place; nothing is redundant or filler.

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 an 8-parameter search tool with an output schema and safety annotations, the description covers the complete call context: when to use it, what data it returns, what happens on no match, how detail scaling works, and a concrete invocation example. Nothing needed for correct selection and invocation 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 description coverage is 100%, so the baseline is 3. The description adds extra meaning by expanding on what each detail level returns (~80 tok vs ~200 tok vs full), giving a concrete query example, and clarifying that top should be kept small for MCP context and latency. That is meaningful value beyond the schema, though not essential because the schema is already strong.

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?

The description opens with a specific verb-resource pair: 'Search MisakaNet's public failure-lesson index by error text, keyword, or topic.' It also explicitly differentiates from the sibling misakanet_get_lesson, telling the agent to prefer that tool for known lesson IDs. This makes the tool's scope unmistakable.

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?

The description gives direct routing guidance: 'run it first when you hit an error, before deciding to submit anything' and 'For a known lesson ID or path, prefer misakanet_get_lesson.' It also explains when FAQ results may appear, which helps the agent interpret unexpected result types. This is explicit when-to-use and when-not-to-use guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?