Skip to main content
Glama

jp_lit_search_fulltext

Search OCR full text and metadata of NDL Digital Collection materials, including restricted items. Filter by NDC or classic books, set search field (contentonly, metaonly, all). Cross-check with official interface for completeness.

Instructions

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

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

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

Discloses read-only behavior, cache refresh with force_refresh, and that results include pid. It also mentions the tool does not cover all materials and is not exhaustive. Without annotations, this provides valuable behavioral context, though could note that results are paginated via from/size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph containing all information, but it is somewhat lengthy and could be broken into sections for readability. However, every sentence provides necessary context, so it is not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description mentions that results contain pid and references sibling tools for further detail. It covers the key aspects of the tool's behavior and limitations. With no output schema provided, the description compensates by indicating result contents.

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 coverage is 100% so baseline is 3. Description adds value by explaining normalization of f_ndc (prefix matching), the meaning of searchfield enum values, and the caching behavior for force_refresh. These go beyond the schema descriptions.

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 it searches OCR full text of digital library materials, specifying the scope (次世代デジタルライブラリー) and differentiating from the main search API. It also mentions the searchfield options that define whether to search content, metadata, or both.

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?

Explicitly states when to use this tool vs alternatives: it is not for comprehensive coverage, warns against concluding no hits, and advises using the official search screen for completeness. It also directs to sibling tools jp_lit_search_pages and jp_lit_get_text_coordinates for page-level details.

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