Skip to main content
Glama

jisho_search

Read-onlyIdempotent

Search Jisho.org for Japanese words, kanji, or English translations using a keyword to look up meanings, readings, and dictionary entries.

Instructions

Search Jisho.org Japanese dictionary for words, kanji, or English translations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "jisho_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch keyword (English, Japanese, romaji).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety and network profile is covered. The description adds no behavior beyond that — no mention of result counts, rate limits, or how kanji vs. word searches differ in response shape.

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?

A single front-loaded sentence with zero padding; the verb and resource appear first and the scope qualifier follows immediately.

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

Completeness3/5

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

For a simple one-parameter search with rich annotations and no output schema, the description is minimally adequate but omits anything about what results look like (readings, parts of speech, kanji details) or result limits, which an agent calling a dictionary would benefit from knowing.

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?

Only one parameter with 100% schema coverage, so the schema already explains 'keyword'. The description usefully clarifies the accepted input modes (English, Japanese, romaji), which maps directly onto the single parameter and adds practical meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Search') and a specific resource ('Jisho.org Japanese dictionary') plus the three lookup modes (words, kanji, English translations). It does not, however, distinguish itself from sibling dictionary tools such as dictionary_lookup or wiktionary_lookup, leaving an agent to guess which dictionary to call.

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

Usage Guidelines2/5

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

The description says what it searches but never when to prefer it over the numerous sibling lookup tools (dictionary_lookup, wiktionary_lookup, jisho's own scope for kanji vs. English). No prerequisites, exclusions, or alternatives are named.

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

Deploy Server

Other Tools