Skip to main content
Glama

jp_lit_search_fulltext

Search OCR full-text and metadata across NDL Digital Collections. Filter results by search field, NDC classification, or classic book flag to locate documents.

Instructions

external read / local bookkeeping write(非破壊)。次世代デジタルライブラリー収録資料を対象に OCR 全文テキストからキーワード検索する。デジコレ本体の全文検索画面/APIではなく、デジコレ本体の「ログインなしで閲覧可能」資料全体も対象ではない。館内限定・送信サービス限定資料を含め、公式検索画面の全文ヒットは網羅しない。網羅性が必要な調査では、この結果だけで「デジコレ全文にヒットなし」と断定せず、公式画面でのブラウザ検索・手動確認を併用する。searchfield=contentonly で本文のみ、metaonly でメタデータのみ、all で両方を検索。結果には pid が含まれ、特定資料内のページ特定は jp_lit_search_pages、ページ画像と OCR 座標確認は jp_lit_get_text_coordinates で行う 外部sourceは変更しない。cache hitでもlocal session履歴を更新し、cache missまたはforce_refreshではlocal cacheを作成・置換する。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNo検索結果の offset。0 始まり。
sizeNo返す資料候補の最大件数。最大 100。
f_ndcNo次世代デジタルライブラリー Book API の f-ndc filter。上位分類は 9* のような前方一致で指定する。9 のような1-2桁の数字だけを渡した場合は 9* に正規化する。空文字・空白だけの値は未指定扱いにする。
keywordYesNDL デジタルコレクション公開範囲の OCR / メタデータから探す語。
searchfieldNo検索対象。contentonly は本文 OCR、metaonly はメタデータ、all は両方。contentonly
fc_is_classicNo古典籍フラグで絞る場合に指定する。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawYes
fromYes
cacheNo
itemsYes
totalYes
keywordYes
searchfieldYes
Behavior5/5

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

The description openly states 'external read / local bookkeeping write(非破壊)' matching annotations (destructiveHint=false). It details that cache hits update local session history, while cache misses or force_refresh create/replace local cache. This adds context beyond annotations, which only provide boolean hints.

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 relatively long but well-structured, starting with purpose, then limitations, usage advice, parameter details, and related tools. It could be slightly more concise, but given the complexity of the tool, the structure is effective.

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?

The description covers the tool's purpose, limitations, usage guidelines, parameter behavior, and follow-up tools. It is complete for a search tool with an output schema (present according to context signals) and complex constraints.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by clarifying edge cases for f_ndc (e.g., normalization of '9' to '9*') and explaining searchfield enum options. This extra detail justifies a 4.

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 performs keyword search on OCR full text of the next-generation digital library collection. It specifies what is NOT included (official search API, all login-free materials), and distinguishes from sibling tools by directing to jp_lit_search_pages and jp_lit_get_text_coordinates for further steps.

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?

Explicit guidance is provided: states that external source is not modified, advises not to conclude 'no hit' based solely on this tool for exhaustive research, and recommends combining with official screen browser search. Additionally, it explains cache behavior with conditions for force_refresh.

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