Skip to main content
Glama

MisakaNet

by org.misakanet
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
idNoLesson ID, usually the filename without .md, e.g. auto-merge-ci-pipeline. Either id or path is required.
pathNoLesson 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

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
errorNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed4 schema fields changed
    • 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"
+}
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, and the description adds substantial behavioral detail beyond that: path precedence, strict path validation, 5000-char truncation with a full_content_url, and distinct error codes with retry semantics. It also warns that truncation can cut before the Verification section.

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 dense but every sentence earns its place: purpose, usage context, argument rules, return shape, error semantics, truncation behavior, and an example. It is front-loaded with the retrieval intent and structured so an agent can quickly extract the key constraints.

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 tool with two parameters, an output schema, and nuanced error/truncation behavior, the description covers everything an agent needs: when to call, what to pass, what to expect, and how to recover from each failure mode. The example further anchors correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning beyond the schema: path takes precedence when both are supplied, path must be a lesson file under lessons/ ending in .md, and id is usually the filename without .md. These details materially change how an agent should construct arguments.

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 clear verb and resource: 'Fetch one public MisakaNet lesson by repository path or lesson ID.' It also differentiates from sibling tools by explicitly positioning this as the post-search retrieval step, distinct from misakanet_search and misakanet_write_lesson.

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 states exactly when to use it ('Use after misakanet_search returns a promising result'), how to supply arguments ('exactly one of id or path'), and how to respond to each error code ('lesson_not_found... do not retry, search instead'). This is explicit, actionable routing guidance.

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

All MisakaNet toolsInspect
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