MisakaNet

misakanet_get_lesson

Read-onlyIdempotent

[RETRIEVAL / READ] Fetch one public MisakaNet lesson by repository path or lesson ID. Use after misakanet_search returns a promising result to pull the full fix content. Provide exactly one of id or path (path takes precedence if both are supplied); if neither is supplied the tool returns {error}. path must be a lesson file (lessons//.md) — anything else is refused with code=invalid_lesson_path rather than read. Returns: object {path: string, content: string} — lesson markdown body, capped at 5000 chars per call; or {error, code}. The code says which: lesson_not_found (no such lesson — do not retry, search instead), invalid_lesson_path (the argument is not a lesson reference — fix the argument), internal_error (a service fault — retrying is reasonable). When the lesson is longer than the cap the response says so instead of pretending to be complete: {truncated: true, content_length: , content_returned: , full_content_url: } — fetch that URL when the tail matters (the cut can fall before the Verification section). Example: misakanet_get_lesson(id='auto-merge-ci-pipeline')

Input Schema

Name	Required	Description	Default
`id`	No	Lesson ID, usually the filename without .md, e.g. auto-merge-ci-pipeline. Either id or path is required.
`path`	No	Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md — must be a file under lessons/ ending in .md (other repository files are not readable through this tool). Either path or id is required.

Output Schema

Name	Required	Description	Default
`path`	No
`error`	No
`content`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

removedInput schema / minProperties
```
Removed value: -1
```

addedInput schema / oneOf

Added value: +[
+  {
+    "required": [
+      "path"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "required": [
+      "path",
+      "id"
+    ]
+  }
+]

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / path / description

Previous value: -"Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md. Either path or id is required."New value: +"Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md — must be a file under lessons/ ending in .md (other repository files are not readable through this tool). Either path or id is required."

Changed4 schema fields changedSep 3, 2026

addedInput schema / minProperties
```
Added value: +1
```

changedInput schema / properties / id / description

Previous value: -"Lesson ID, usually the filename without .md, e.g. auto-merge-ci-pipeline."New value: +"Lesson ID, usually the filename without .md, e.g. auto-merge-ci-pipeline. Either id or path is required."

changedInput schema / properties / path / description

Previous value: -"Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md."New value: +"Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md. Either path or id is required."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "path": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavior beyond them: the 5000-char content cap, faithful truncation reporting with a full_content_url escape hatch, path-validation refusal with code=invalid_lesson_path, the argument-precedence rule, and per-code retry semantics. This is the kind of disclosure an agent needs to avoid mis-handling failures.

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-loads the [RETRIEVAL / READ] tag and the core action, then layers usage, argument rules, and return/error semantics in a logical order with zero filler sentences. It runs long and re-documents return shapes already covered by the output schema, which costs a point, but every 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?

For a two-param read tool with a published output schema, the description covers everything an agent needs: selection criteria, argument precedence, validation limits, truncation handling, and error-code triage. Nothing material to invoking it correctly is left implicit.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the "provide exactly one of id or path, path takes precedence if both are supplied" precedence rule, the neither-supplied error behavior, and the constraint that only lessons/<topic>/<slug>.md files are readable. These resolve genuine ambiguity in the oneOf schema (which oddly permits both).

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+resource ("Fetch one public MisakaNet lesson by repository path or lesson ID") and immediately differentiates itself from the sibling misakanet_search by naming the handoff relationship. An agent can separate this retrieval tool from search/write siblings without reading the 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?

Explicitly says when to use it ("after misakanet_search returns a promising result to pull the full fix content") and encodes the alternative in the error guidance itself ("lesson_not_found — do not retry, search instead"). When-not-to-retry conditions are spelled out per error code, which is unusually actionable.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?