Skip to main content
Glama

DinCat — learning and life in Japan

Search the DinCat library

search_library
Read-onlyIdempotent

Search DinCat's library of ready-made question pages by keyword, in the user's language (e.g. 手取り, 永住, 敬語, JLPT, 年末調整, 到手, take-home pay). Returns up to 8 pages with links that open the question in DinCat's chat; if nothing matches, returns the shelves instead.

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": {
      "query": "<query>"
    },
    "name": "search_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the reply and of the linked pages: ja = Japanese, zh = Simplified Chinese, en = English. Use the user's language.ja
queryYesKeyword(s) in the user's language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered. The description adds genuinely new behavior: a cap of 8 results, links that open the question inside DinCat's chat, and a non-error fallback that returns shelves when nothing matches — telling the agent it need not handle an empty-result failure.

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 tightly packed sentences with the core action and scope first, followed by return behavior and fallback. No filler, and every clause carries information the agent can act on.

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?

With only two params, full schema coverage, and no output schema, the description closes the remaining gaps by explaining result count, link behavior, and the empty-match case. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so both query and lang (including the ja/zh/en enum) are already fully documented in the schema. The description's multilingual keyword examples lightly reinforce cross-language matching but add little beyond the schema baseline.

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 and resource ('Search DinCat's library of ready-made question pages by keyword') and scopes it further with a return limit and a fallback. It never names a sibling such as list_library, so the differentiation from browsing-the-shelves tools is implied rather than explicit.

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?

Clear context for use: keyword search in the user's language, with multilingual example terms that show what a valid query looks like. It does not state when to prefer list_library or another lookup path, so exclusions are absent, but the intended situation is unambiguous.

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.

Resources