Skip to main content
Glama

jp_lit_export_session

Export current or past research sessions from Japanese literature searches as Markdown, JSON, or CSL-JSON files for human review or reference management.

Instructions

export/write file。現在の調査セッション、または session_id で指定した過去セッションを repo 内の exports/ または output_path に書き出す。既定は Markdown で、人間が読み返しやすい形に整形する。session は読み取るだけで変更しない。cache 一覧や再抽出結果だけを書き出す場合は jp_lit_export_view を使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNo書き出す過去セッションID。未指定なら現在の調査セッションを書き出す。
formatNo出力形式。markdown は人間向け、json は完全な構造化ログ、csl-json は文献管理向け。markdown
profileNo書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補。full_log
output_pathNo出力先ファイルパス。未指定なら repo 内 exports/ に自動生成する。
include_unselectedNomarkdown/json の full_log で未選別候補を含めるかどうか。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
formatYes
profileYes
pathYes
exported_atYes
item_countYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the session is read-only and not changed, but lacks details on synchronous behavior, overwrite policy, required permissions, or return value format. Adequate but not thorough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, using two short sentences to convey purpose, scope, default, and alternative. No fluff, front-loaded with key information.

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 5 parameters and existence of output schema, the description covers purpose, alternative, and basic behavior. It lacks details on output schema contents, error states, or file overwriting, but overall complete for typical usage.

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 100%, so baseline is 3. The description adds minimal value beyond schema: it mentions default format and human readability but does not clarify parameter interactions or constraints further.

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 exports/writes file for current or past sessions, with default Markdown formatting. It explicitly distinguishes from sibling jp_lit_export_view by noting that tool is for cache/re-extraction results.

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 provides explicit guidance on when to use this tool (export session) and when not (use jp_lit_export_view for cache/re-extraction). Also notes default behavior and human-readable formatting.

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