Skip to main content
Glama

jp_lit_search_pages

Search inside Japanese digital library pages by keyword to retrieve page images and OCR text. Supports NDL, CiNii, and other academic databases.

Instructions

external read / local bookkeeping write(非破壊)。NDL デジタルコレクション資料内のページをキーワードで全文検索する(インターネット公開資料のみ)。source_id を使う場合は事前に jp_lit_get_record で next_digital_library.available=true を確認すること。全資料から候補 pid を探す段階では jp_lit_search_fulltext、特定ページの OCR テキストと画像 URL 確認は jp_lit_get_text_coordinates を使う。jp_lit_search_fulltext の結果の pid はそのまま渡してよい 外部sourceは変更しない。cache hitでもlocal session履歴を更新し、cache missまたはforce_refreshではlocal cacheを作成・置換する。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidNo次世代デジタルライブラリーの pid。jp_lit_search_fulltext の結果から直接渡せる。
fromNo検索結果の offset。0 始まり。
sizeNo返すページ一致の最大件数。最大 100。
sourceYes通常は ndl_digital。source_id を使う場合は jp_lit_get_record で OCR 利用可否を確認してから指定する。
keywordYes資料内 OCR テキストから探す語。
source_idNoNDL デジタルコレクションの source_id。pid が分かる場合は pid を優先できる。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYes
rawYes
fromYes
cacheNo
itemsNo
totalYes
keywordYes
Behavior5/5

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

The description reveals local bookkeeping write behavior (non-destructive), cache update/creation logic, and explicitly states that external sources are not modified. This goes beyond annotations (readOnlyHint=false, destructiveHint=false) by detailing the caching side effects.

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?

The description is a single paragraph with clear logical flow: purpose, prerequisite, sibling tool usage, pid hint, external resource guarantee, and caching behavior. Every sentence adds necessary information without redundancy.

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?

While the description covers prerequisites and sibling relationships, it does not clarify the behavior when both pid and source_id are omitted (they are optional in schema). The tool could potentially search across all materials? This missing guidance reduces completeness.

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% with parameter descriptions. The description adds limited extra semantics: that source_id requires prior availability check and that pid from jp_lit_search_fulltext can be passed directly. This adds marginal value over the schema.

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 full-text search of pages within NDL Digital Collection materials (internet-published only). It distinguishes from siblings by specifying jp_lit_search_fulltext for finding candidate pids across all materials and jp_lit_get_text_coordinates for OCR text and image URL confirmation.

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: prerequisite check with jp_lit_get_record before using source_id, and clear instructions on when to use jp_lit_search_fulltext (to find candidate pids) and jp_lit_get_text_coordinates (for page-level OCR and image URLs).

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