Skip to main content
Glama

AutoTasker Hub — China Social Data API

jisho_search

Japanese dictionary (Jisho): readings, JLPT level, English definitions, parts of speech. $0.01 USDC.

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
limitNo
keywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add two genuinely useful facts: the shape of the results (readings, JLPT, definitions, POS) and that the call costs $0.01 USDC. It omits other behavior an agent needs, such as accepted keyword scripts (kanji/kana/romaji/English) and matching semantics.

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?

Two compact fragments with no filler; the substantive capability and the price are both front-loaded. It is terse to the point of under-specification, but nothing present is wasted.

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 two-parameter lookup with no annotations and no output schema, the description usefully sketches the return payload and the cost. The critical gap is input semantics — an agent cannot tell whether to pass kanji, kana, romaji, or English, which is exactly what the missing schema coverage would otherwise supply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate — and it does not. It never says what form 'keyword' takes (Japanese characters, romaji, or English gloss) or what 'limit' controls, leaving the only required parameter ambiguous.

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?

The description names the resource concretely ('Japanese dictionary (Jisho)') and enumerates the returned data (readings, JLPT level, English definitions, parts of speech), which is enough to separate it from English-oriented siblings like define_word or datamuse_synonyms. It stops short of a clean verb+resource statement because the action ('search') is only carried by the tool name.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for looking up Japanese words, and the '(Jisho)' source hints at its scope. There is no explicit when-to-use, when-not-to-use, or comparison to the other word/dictionary siblings, so routing still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.