Skip to main content
Glama

jp_lit_get_record

Retrieve detailed metadata and official URLs for a record from Japanese literature databases by specifying source and record ID. Supports multiple sources including NDL, CiNii, and national archives.

Instructions

文献レコード詳細を取得する。source=national_archives / jacar は目録メタデータと公式レコードURLを返し、画像本体・IIIF・OCR本文は取得しない。source=nijl_articles は国文学論文DBのHTMLから書誌メタデータと公式レコードURLを best-effort で返し、本文・PDF・OPAC追跡は取得しない。source=kokusho は国書DBのJSONから書誌・著作・所在・公式URL・manifest URL 等のメタデータを返し、manifest 本体・画像・OCR は取得しない。source=ninjal_bibliography は日本語研究・日本語教育文献DBのHTMLから書誌メタデータと本文リンクURLを best-effort で返し、本文自体は取得しない。source=ndl_digital の場合、source_metadata.next_digital_library.available=true であれば jp_lit_get_text_coordinates / jp_lit_get_fulltext / jp_lit_search_pages が利用可能。false の場合は OCR 系ツールを利用できない。実務上は次世代側未収録であることが多いが、現実装ではアクセス制限等との厳密な区別はしていない

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes検索・取得・記録対象の情報源ID。jp_lit_search の結果や source plan に含まれる source を指定する。
source_idYessource 内のレコードID。jp_lit_search の items[].source_id を指定する。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
source_idYes
titleYes
subtitleYes
title_readingYes
authorsYes
publisherYes
journal_titleYes
issued_atYes
issued_at_labelYes
issued_at_precisionYes
summaryYes
urlYes
availabilityYes
alternative_titlesYes
publication_placeYes
languageYes
material_typeYes
extentYes
subjectsYes
identifiersYes
table_of_contentsYes
content_accessYes
source_metadataYes
rawYes
cacheNo
Behavior4/5

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

With no annotations, the description fully bears the burden and details what is and isn't returned per source, caching behavior via force_refresh, and implementation limitations (access restrictions not distinguished). Lacks explicit error/rate limit info, but covers key behaviors.

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 detailed and front-loaded with the main purpose, then structured per source. Each sentence adds value, though longer than necessary; still effective.

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 complexity of multiple sources and the existence of an output schema, the description covers all essential behaviors, limitations, and follow-up tool mentions, making it complete for agent decision-making.

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?

Schema coverage is 100%, but the description adds significant value: it explains source-specific behavior, ties source_id to search results, and clarifies force_refresh cache use, going well beyond the schema's 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 retrieves record details and explicitly lists what each source returns/does not return, distinguishing it from sibling tools like search or fulltext retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool per source, including best-effort notes and follow-up actions (e.g., OCR tools availability). However, it does not explicitly contrast with sibling tools.

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