Skip to main content
Glama

jp_lit_search

Search Japanese literature across NDL, CiNii, J-STAGE, and other academic databases with a single query, covering articles, books, and historical records.

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
Behavior3/5

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

Without annotations, the description carries the burden. It discloses that ndl_digital results include non-public metadata and advises checking source_metadata before using OCR tools. It does not mention rate limits, authentication, or statelessness. The description adds moderate behavioral context but is not fully comprehensive.

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 well-structured with key information front-loaded. It concisely covers purpose, usage, and source mapping without excessive verbosity. While it is relatively long, each sentence adds value.

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?

With an output schema present, the description can omit return values, but it still needs to cover parameter usage. It adequately addresses source selection but leaves many parameters (filters, sort, date range) undocumented. The description is not fully complete given the tool's complexity.

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%, so the description must compensate. It provides limited parameter information: it explains the implicit semantics of 'source' via mapping, and clarifies that total/limit/page are per-call values. However, it does not explain query, limit, page defaults, sort_by, filters, or other parameters in detail.

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 clearly states the tool's purpose: searching a Japanese literature portal with cross-search of 8 sources by default. It specifies which sources are excluded from default and provides a mapping for user phrases. However, it does not explicitly differentiate from sibling tools like jp_lit_search_fulltext, though the context implies it's the main search tool.

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?

The description provides explicit guidance on source selection, including default behavior and when to use excluded sources. It also explains user phrase mapping for source selection. However, it does not offer guidance on when to use this tool versus its siblings, and it lacks information on prerequisites or typical usage scenarios.

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