Loading ToolBench
Jisho.org Japanese-English dictionary MCP (keyless). Wraps the public Jisho.org API. Look up Japanese words by kanji, kana, or romaji, or translate English -> Japanese. Returns readings, English meanings, parts of speech, JLPT level, and whether a word is "common".
Two well-named, read-only tools with clear descriptions (194 - 250 chars, within baseline 34 - 392). Both have complete input schemas with typed parameters and descriptions. Output schemas are partially documented in descriptions but not formally specified. Error handling is basic (returns error objects but lacks recovery guidance). No tool annotations (readOnlyHint, etc.). Naming follows verb_noun pattern (search_words, lookup). Parameters are well-described with examples and constraints. Main gaps: no formal output schema documentation, no error classification or recovery hints, missing tool annotations.
Look up a single Japanese or English word in the Jisho.org dictionary and return only the single best/first matching entry in a compact form: headword (slug), common-ness, JLPT level, all readings, a flat list of English meanings, and the unique parts of speech. Best for quick "what does this word mean / how is it read" questions. Accepts kanji, kana, romaji, or English.
Search the Jisho.org Japanese<->English dictionary. The keyword can be English (translate to Japanese), Japanese kanji/kana, or romaji. Returns up to `limit` matching dictionary entries, each with the headword (slug), whether it is a common word, JLPT level, all readings/spellings, and English meanings grouped into senses with parts of speech. Use this to translate, look up a kanji/kana word, or find Japanese words for an English concept.
Output schemas not formally documented. Descriptions mention returned fields (slug, is_common, jlpt, readings, meanings, parts_of_speech) but no JSON Schema definition provided for LLM planning.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Both tools are read-only and idempotent but lack explicit hints for agent planning.
Error responses lack recovery guidance. When no entry found or API fails, errors return bare messages ('no entry found', 'Jisho: 404') without suggesting next steps or alternatives.
search_words limit parameter accepts number but defaults to 10 and clamps to 100. No explicit min/max documented in parameter description; LLM must infer from code.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
No pagination or result count limit enforcement in descriptions. search_words returns up to limit items but no guidance on typical result sizes or when to paginate.