Japanese Skills · 言の葉

Find a Japanese grammar point

find_grammar

Read-onlyIdempotent

Use this when the user asks about a Japanese grammar pattern or particle (〜てもいい, ために, ば vs たら, は and が), what it means, how it is used, an example of it, or how to say something with a pattern. Searches the site’s 828 grammar points (N5–N1) by the pattern in Japanese or romaji, or by its meaning in the user’s language. Each result has the pattern, JLPT level, meaning in the user’s language, an example sentence with translation, a recording of the example where available, and the grammar page; plus the site’s course lessons whose titles match, with links and whether each is free or needs a subscription or pass.

Input Schema

Name	Required	Description
`lang`	No	The 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.
`level`	No	Only this JLPT level.
`limit`	No	How many grammar points to return at most.
`query`	Yes	The pattern (てもいい, 〜ために, te mo ii) or what it expresses in the user’s language (permission, “in order to”, 为了).

Output Schema

Name	Required	Description	Default
`lang`	Yes
`query`	Yes
`lessons`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "lang": {
+      "enum": [
+        "zh-Hans",
+        "zh-Hant",
+        "en",
+        "ko"
+      ],
+      "type": "string"
+    },
+    "lessons": {
+      "items": {
+        "properties": {
+          "course": {
+            "type": "string"
+          },
+          "free": {
+            "description": "false: needs a subscription or pass",
+            "type": "boolean"
+          },
+          "lesson": {
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "course",
+          "lesson",
+          "title",
+          "free",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "example": {
+            "properties": {
+              "audio": {
+                "description": "Recordings of the site’s two voices, or null when there is none",
+                "properties": {
+                  "voice1": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "voice2": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  }
+                },
+                "required": [
+                  "voice1",
+                  "voice2"
+                ],
+                "type": [
+                  "object",
+                  "null"
+                ]
+              },
+              "japanese": {
+                "type": "string"
+              },
+              "translation": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "japanese",
+              "translation",
+              "audio"
+            ],
+            "type": "object"
+          },
+          "level": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "pattern": {
+            "type": "string"
+          },
+          "url": {
+            "description": "The grammar point on its page",
+            "type": "string"
+          }
+        },
+        "required": [
+          "pattern",
+          "level",
+          "meaning",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "lang",
+    "results",
+    "lessons"
+  ],
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive lookup behavior. The description adds valuable context beyond those annotations: the corpus size (828 points, N5–N1), result contents including translations, example recordings where available, grammar page links, and course lessons with free/subscription/pass status.

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 the usage trigger and is well organized across three sentences. It is somewhat long because it enumerates result contents in detail, but the information is relevant and not repetitive.

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?

Given the lookup nature, annotations, complete schema, and output schema, the description is sufficiently complete. It explains when to use the tool, what it searches, what the results include, and that matching course lessons are also returned.

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 query, lang, level, and limit thoroughly. The description reinforces that the query can be a Japanese/romaji pattern or a meaning in the user's language, but it does not add significant semantics beyond what the schema provides.

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 uses a specific verb/resource combination: it finds Japanese grammar points and searches 828 grammar points by pattern or meaning. The examples (〜てもいい, ために, ば vs たら, は and が) make it clearly distinct from sibling tools like lookup_word, lookup_kanji, and list_courses.

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?

It gives a clear trigger: 'Use this when the user asks about a Japanese grammar pattern or particle…'. It covers meaning, usage, examples, and how to express something with a pattern, but does not explicitly name when not to use it or route to alternatives.

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

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