Skip to main content
Glama

Japanese Skills · 言の葉

by io.github.Keith-CY
OverviewDiscussionsAdmin

JLPT levels and courses

list_courses
Read-onlyIdempotent

Use this when the user asks how to study Japanese or prepare for a JLPT level with Japanese Skills · 言の葉, or what study material the site has. Lists the study library (sections, counts and links), the JLPT practice levels (number of questions; links for the free ones), and the 15 courses with their level, number of lessons and link. With course, lists that course’s lessons with titles and links. Each level, course and lesson is labelled free or needs a subscription or pass.

Input Schema

NameRequiredDescriptionDefault
langNoThe user’s language for meanings, labels and links: zh-Hans (Simplified Chinese), zh-Hant (Traditional Chinese), en (English) or ko (Korean). Other languages: en. Default: guessed from the query.
courseNoA course id from this tool’s list (e.g. "n5", "kanji", "keigo") to list its lessons.

Output Schema

NameRequiredDescriptionDefault
jlptNo
langYes
courseNoWith course: that course and its lessons
coursesNo
libraryNo
coursesUrlNo
studyRouteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "course": {
+      "description": "With course: that course and its lessons",
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "lessons": {
+          "items": {
+            "properties": {
+              "free": {
+                "description": "false: needs a subscription or pass",
+                "type": "boolean"
+              },
+              "lesson": {
+                "type": "integer"
+              },
+              "level": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "lesson",
+              "title",
+              "free",
+              "url"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "level": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "level",
+        "summary",
+        "url",
+        "lessons"
+      ],
+      "type": "object"
+    },
+    "courses": {
+      "items": {
+        "properties": {
+          "freeLessons": {
+            "type": "integer"
+          },
+          "id": {
+            "description": "Pass as course to list the lessons",
+            "type": "string"
+          },
+          "lessons": {
+            "type": "integer"
+          },
+          "level": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "level",
+          "lessons",
+          "freeLessons",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "coursesUrl": {
+      "type": "string"
+    },
+    "jlpt": {
+      "items": {
+        "properties": {
+          "free": {
+            "description": "false: needs a subscription or pass",
+            "type": "boolean"
+          },
+          "level": {
+            "type": "string"
+          },
+          "questions": {
+            "type": "integer"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "level",
+          "questions",
+          "free"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lang": {
+      "enum": [
+        "zh-Hans",
+        "zh-Hant",
+        "en",
+        "ko"
+      ],
+      "type": "string"
+    },
+    "library": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "count",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "studyRoute": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "lang"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is lower, and the description still adds real context: it enumerates the returned content and notes that each level, course and lesson is labelled free or needs a subscription or pass. That monetization/labeling detail is not derivable from annotations or the schema. It stops short of describing pagination or response size.

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?

Three sentences, each carrying distinct information: usage trigger first, then default output, then the course-scoped variant, then the free/paid labeling. Front-loaded and free of filler. Slightly dense/long but every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, yet the description outlines them anyway along with the conditional lesson-listing behavior and free/paid labeling. Combined with fully documented parameters and read-only annotations, an agent has what it needs to call this correctly; only minor gaps like result volume remain.

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 lang (enum with fallback behavior) and course (id from this tool's list, max length). The description only adds that supplying course switches the output to that course's lessons with titles and links, which is a modest semantic addition rather than new parameter mechanics. Baseline 3 is the right level here.

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 (lists) and precisely enumerates what is listed: study library sections with counts and links, JLPT practice levels with question counts, and 15 courses with level/lesson count/link, plus a course-scoped lesson listing. This is clearly distinguishable from the sibling lookup tools (find_grammar, lookup_kanji, lookup_word), which target individual items rather than a course/level catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: 'Use this when the user asks how to study Japanese or prepare for a JLPT level ... or what study material the site has.' That is a clear when-to-use condition. It does not name sibling alternatives or state when-not to use this tool, so it falls short of a 5, but an agent has enough to route correctly.

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

All Japanese Skills · 言の葉 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