Skip to main content
Glama

jp_lit_search

Unified search across 8 major Japanese literature databases including NDL, CiNii, and J-STAGE. Optionally include specialized sources for archives, classical texts, or linguistics.

Instructions

日本語文献ポータルを検索する。source 未指定で8ソース横断。national_archives / jacar / nijl_articles / kokusho / ninjal_bibliography は既定横断に含めず、公文書・外交・軍事・旧外地資料、国文学論文、古典籍、日本語研究文献などで明示指定された場合のみ使う。ユーザーの言い回しから source を読み替える: 「NDL/国会図書館」→ndl_catalog、「デジコレ/NDLデジタル」→ndl_digital、「CiNii論文」→cinii_articles、「CiNii図書/大学図書館」→cinii_books、「J-STAGE」→jstage_articles、「機関リポジトリ/IRDB」→irdb、「国会会議録」→kokkai_minutes、「帝国議会」→teikoku_minutes、「人文専門DB/nihu_bridge」→nihu_bridge、「Japan Search/ジャパンサーチ」→japan_search、「国立公文書館/特定歴史公文書/太政官/省庁資料」→national_archives、「JACAR/アジア歴史資料/外交/軍事/旧外地/植民地/朝鮮/台湾/関東州」→jacar、「国文学論文/国文研論文/日本文学研究論文」→nijl_articles、「国書/古典籍/写本/版本」→kokusho、「日本語研究/日本語教育文献/国語教育文献」→ninjal_bibliography。total / limit / page はこの 1 回の検索呼び出し単位の値であり、Skill が複数回検索して要約する場合は各回ごとに読む。source=ndl_digital の結果にはインターネット非公開(館内限定・図書館送信)資料のメタデータも含まれる。OCR 系ツールを使う前に jp_lit_get_record で source_metadata.next_digital_library.available を確認すること

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
sourceNo
limitNo
pageNo
sort_byNo
sort_orderNo
force_refreshNo
issued_fromNo
issued_toNo
filtersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
sourceYes
pageYes
limitYes
totalYes
itemsYes
facetsNo
cacheNo
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses behavioral traits such as ndl_digital including restricted metadata, per-call semantics for total/limit/page, and the recommendation to check availability via jp_lit_get_record before OCR. It lacks some details like rate limits or authentication, but is quite transparent.

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?

The description is long but efficiently structured: purpose first, then detailed mapping table, then special notes. Every sentence adds value; there is no redundancy. It could be slightly more concise but is well-organized.

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?

Given the tool's complexity (19 sources, 10 parameters, nested objects), the description covers the primary search behavior and source selection well. However, it lacks explanation for several parameters (e.g., filters, sort options) and does not mention the output schema (though it exists). It is adequate but not fully complete.

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?

The input schema has 0% description coverage, so the description must compensate. It thoroughly explains the 'source' parameter with aliases and default behavior, and touches on total/limit/page semantics. However, it does not explain other parameters like filters, sort_by, force_refresh, or issued_from/to, leaving gaps.

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 a Japanese literature portal, with a specific verb- resource combination. It distinguishes from sibling tools like jp_lit_get_record by focusing on search across multiple sources, and specifies default cross-search behavior.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus not, including which sources are included in the default cross-search and which require explicit specification. It gives detailed mappings from user phrasing to source values, helping the agent select the correct source.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itarunnn/jp-lit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server