Skip to main content
Glama

jp_lit_get_text_coordinates

Retrieve page-level OCR text and coordinate data from NDL Digital Collection internet public materials using pid or source_id.

Instructions

external read / local bookkeeping write(非破壊)。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 はそのまま渡してよい 外部sourceは変更しない。cache hitでもlocal session履歴を更新し、cache missまたはforce_refreshではlocal cacheを作成・置換する。

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

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

Beyond annotations, the description discloses it is non-destructive, does not modify external sources, and explains caching behavior (cache hit updates session, cache miss/force_refresh creates/replaces cache). This adds useful behavioral context.

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 each sentence provides necessary information. It is front-loaded with core purpose and non-destructive nature. Minor improvement could be structuring with bullet points or breaking into sections.

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?

Given the tool's complexity (5 parameters, caching, prerequisites), the description covers all essential aspects: purpose, prerequisites, caching behavior, parameter usage, and alternatives. It is complete enough for the agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 5 parameters have schema descriptions (100% coverage). The description adds value by specifying that pid can be taken directly from jp_lit_search_fulltext results, that source is usually ndl_digital, and clarifying cache behavior for force_refresh.

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 gets OCR text and coordinates for a page from NDL digital collections, with a verb and resource. It distinguishes from siblings by referencing jp_lit_search_pages for page number search and jp_lit_get_fulltext for bulk fulltext.

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?

Provides explicit guidance on when to use source_id (requires prior availability check with jp_lit_get_record), mentions that pid from jp_lit_search_fulltext can be passed directly, and lists alternatives for page numbering and fulltext retrieval.

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