Skip to main content
Glama
Sign In

Jisho

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Words

search_words
Read-onlyIdempotent

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "house"
    },
    "name": "search_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of entries to return (default 10).
keywordYesSearch term: English word/phrase, Japanese kanji or kana, or romaji (e.g. "house", "家", "いえ", "ie").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "house"
+  },
+  {
+    "keyword": "食べる",
+    "limit": 5
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds useful behavioral context: returns up to `limit` entries with specific fields, input types (English, kanji, kana, romaji). No contradiction with annotations.

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?

Two sentences, front-loaded with purpose and input flexibility, then return format and use cases. No unnecessary words, very efficient.

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?

No output schema, but description thoroughly explains return fields (headword, common word flag, JLPT level, readings, meanings with senses and POS). Schema covers both parameters. Complete enough for effective use.

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% with descriptions for both parameters. Description adds extra meaning: keyword can be English, kanji, kana, or romaji, and limit defaults to 10. This goes beyond the schema description.

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 clearly states the tool searches the Jisho.org Japanese-English dictionary, specifies the resource and action, and distinguishes it from sibling tools which are different in scope.

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?

Explicitly states use cases: translate, look up a kanji/kana word, or find Japanese words for an English concept. Does not explicitly mention when not to use or alternatives, but context is clear.

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

All Jisho 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