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: [compact: {id, title, problem, freshness, evidence_level} | summary: + {domain, tags, fix} | full: the record, each with 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.6/5.0

Behavior5/5

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

Annotations already mark this read-only/idempotent, and the description adds useful behavioral context: progressive disclosure token sizes, FAQ results surfacing answered questions, and the no-match shape with suggestion and intake. It also labels the tool as a non-submitting read path.

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?

The description is front-loaded with purpose, then usage routing, then parameter behavior, FAQ caveat, return shape, and an example. It is a bit dense and the Returns section partly duplicates what the output schema would cover, but every section earns its place for a search tool with eight parameters.

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 retrieval/search tool, the description covers what to search, when to run it, when to use the sibling, result depth options, FAQ behavior, no-match handling, and a concrete example. Nothing essential for correct invocation 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 description coverage is 100%, so the schema already documents all eight parameters. The description's detail explanation and example add context but mostly restate what the schema provides; there is no significant new per-parameter semantic info.

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 leads with a specific verb and resource: 'Search MisakaNet's public failure-lesson index by error text, keyword, or topic.' It also labels the tool as the primary read path and explicitly contrasts it with misakanet_get_lesson, so an agent can distinguish it from siblings.

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?

It says to 'run it first when you hit an error, before deciding to submit anything,' and names the condition for the alternative: 'For a known lesson ID or path, prefer misakanet_get_lesson.' 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

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

Need Help?