Skip to main content
Glama

jp_lit_search_pages

Search within NDL Digital Collection documents for pages containing a specific keyword in OCR text. Specify a document by source_id or pid to find matching page results.

Instructions

read-only。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 はそのまま渡してよい

Input Schema

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

Output Schema

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

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

The description declares 'read-only' and notes the constraint of searching only internet public materials. It explains the force_refresh parameter behavior regarding cache. However, without annotations, more details on rate limits, error handling, or performance could further enhance transparency.

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 a single paragraph that efficiently packs all key information, starting with the core read-only purpose, then prerequisites, and relationships to siblings. It is concise but informative.

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?

Given the output schema exists (not shown), the description need not detail return values. It covers the usage flow, constraints, and prerequisites for parameters like source_id. It also places the tool in the context of sibling tools, making the overall workflow clear.

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%, providing baseline 3. The description adds value by explaining that source is normally 'ndl_digital', that pid can be passed directly from jp_lit_search_fulltext, and the relationship between source_id and pid, which goes 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 the tool searches pages within NDL Digital Collection materials by keyword, and specifies it is for internet public materials only. It distinguishes from siblings like jp_lit_search_fulltext (for finding candidate pids) and jp_lit_get_text_coordinates (for OCR text and image URLs).

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 explicitly guides when to use this tool: after obtaining a pid from jp_lit_search_fulltext, or with a source_id after verifying availability via jp_lit_get_record. It also states when to use alternative tools for other stages of the workflow.

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