Skip to main content
Glama

jp_lit_get_record

Retrieves detailed bibliographic metadata and official record URLs from Japanese literature sources (NDL, CiNii, J-STAGE, archives) without returning full text or images.

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
source_idYes
force_refreshNo

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

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

With no annotations, the description fully discloses behavior: it details what metadata is returned per source, explicitly states what is NOT retrieved (images, OCR, fulltext), notes best-effort parsing for some sources, and acknowledges implementation limitations (no strict access restriction distinction).

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 long but well-structured as a per-source list. Every sentence adds necessary detail without redundancy. Could be slightly more concise, but the length is justified by the complexity of the tool.

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 3 parameters (2 required) and an output schema (not detailed), the description comprehensively covers core behavior across sources, linking to sibling tools for one case (ndl_digital). Missing details about 'source_id' and 'force_refresh' leave minor gaps, and output schema is not referenced.

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 0%, so description carries the burden. It thoroughly explains the 'source' parameter by linking each enum value to specific behavior. However, 'source_id' and 'force_refresh' are not described, leaving their purpose implicit. The description adds value for 'source' but fails to cover all parameters.

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 literature record details from multiple Japanese literature sources. It specifies what each source returns and does not return (e.g., no images, no fulltext), distinguishing it clearly from sibling tools like jp_lit_get_fulltext or jp_lit_search_pages.

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 per-source guidance on capabilities and limitations, and for ndl_digital, it points to alternative tools (jp_lit_get_text_coordinates, etc.) when available. However, it does not explicitly state general when-not-to-use scenarios or high-level comparisons with all siblings.

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