Skip to main content
Glama

jp_lit_get_text_coordinates

Retrieve OCR text and coordinate data for a specific page from NDL Digital Collection materials. Use source_id or pid to access publicly available resources.

Instructions

read-only。NDL デジタルコレクション資料のページ単位 OCR テキストと座標を取得する(インターネット公開資料のみ)。source_id を使う場合は事前に jp_lit_get_record で next_digital_library.available=true を確認すること。ページ番号を探す段階では jp_lit_search_pages、全文一括取得は jp_lit_get_fulltext を使う。jp_lit_search_fulltext の結果の pid はそのまま渡してよい

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidNo次世代デジタルライブラリーの pid。jp_lit_search_fulltext の結果から直接渡せる。
pageYes取得するページ番号。1 始まり。
sourceYes通常は ndl_digital。source_id を使う場合は jp_lit_get_record で OCR 利用可否を確認してから指定する。
source_idNoNDL デジタルコレクションの source_id。pid が分かる場合は pid を優先できる。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYes
rawYes
pageYes
cacheNo
contentsNo
coordjsonNo
page_image_urlYes
Behavior3/5

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

The description states the tool is read-only and limited to internet public materials, which is good. However, it does not mention caching behavior (despite the force_refresh parameter), error conditions, or any other side effects. Since no annotations are provided, the description carries the full burden but leaves gaps.

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 concise with a clear, front-loaded purpose. It uses minimal sentences to convey essential information, though it could be slightly more streamlined without losing value.

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 tool has 5 parameters, an output schema, and siblings, the description is fairly complete: it covers scope, preconditions, alternatives, and usage hints. It does not need to explain return values due to output schema existence.

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 covers all 5 parameters with descriptions (100%), so baseline is 3. The description adds value by clarifying that source_id requires a prerequisite check and that pid from jp_lit_search_fulltext can be passed directly, going beyond 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 verb (get), resource (page-level OCR text and coordinates), and scope (NDL digital collection, internet public only). It also distinguishes from siblings by mentioning alternatives for page finding and full-text.

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 (page-level OCR), when not to (use jp_lit_get_fulltext for batch, jp_lit_search_pages for page numbers), and provides a precondition (check availability via jp_lit_get_record for source_id).

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