Skip to main content
Glama

jp_lit_export_session

Export a specified literature research session as Markdown, JSON, or CSL-JSON to exports/ or a chosen path without altering the session.

Instructions

export/write file。session_id で明示した調査セッションを MCPサーバーの作業ディレクトリ(cwd)内の exports/ または output_path に書き出す。既定は Markdown で、人間が読み返しやすい形に整形する。session は読み取るだけで変更しない。cache 一覧や再抽出結果だけを書き出す場合は jp_lit_export_view を使う

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "jp_lit_export_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo出力形式。markdown は人間向け、json は完全な構造化ログ、csl-json は文献管理向け。markdown
profileNo書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補、methods は保存された検索方法(markdown/json)。full_log
overwriteNotrue の場合のみ既存ファイルの上書きを許可する。
session_idYes書き出す調査セッションID。
output_pathNo出力先ファイルパス。未指定なら MCPサーバーの作業ディレクトリ(cwd)内の exports/ に自動生成する。
include_unselectedNomarkdown/json の full_log で未選別候補を含めるかどうか。
allow_external_pathNotrue の場合のみ MCPサーバーの作業ディレクトリ(cwd)内の exports/ 外への書き出しを許可する。

Output Schema

NameRequiredDescriptionDefault
pathYes
formatYes
profileYes
item_countYes
session_idYes
exported_atYes
search_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.19.1
    • changedInput schema / properties / allow_external_path / description
      Previous value: -"true の場合のみ repo 内 exports/ 外への書き出しを許可する。"New value: +"true の場合のみ MCPサーバーの作業ディレクトリ(cwd)内の exports/ 外への書き出しを許可する。"
    • changedInput schema / properties / output_path / description
      Previous value: -"出力先ファイルパス。未指定なら repo 内 exports/ に自動生成する。"New value: +"出力先ファイルパス。未指定なら MCPサーバーの作業ディレクトリ(cwd)内の exports/ に自動生成する。"
  2. Changed4 schema fields changedv0.19.0
    • changedInput schema / properties / profile / description
      Previous value: -"書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補。"New value: +"書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補、methods は保存された検索方法(markdown/json)。"
    • changedInput schema / properties / profile / enum
      Previous value: -[
      -  "full_log",
      -  "selected",
      -  "unselected"
      -]New value: +[
      +  "full_log",
      +  "selected",
      +  "unselected",
      +  "methods"
      +]
    • changedOutput schema / properties / profile / enum
      Previous value: -[
      -  "full_log",
      -  "selected",
      -  "unselected"
      -]New value: +[
      +  "full_log",
      +  "selected",
      +  "unselected",
      +  "methods"
      +]
    • addedOutput schema / properties / search_count
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
  3. Changed2 schema fields changedv0.13.0
    • changedInput schema / properties / session_id / description
      Previous value: -"書き出す過去セッションID。未指定なら現在の調査セッションを書き出す。"New value: +"書き出す調査セッションID。"
    • addedInput schema / required
      Added value: +[
      +  "session_id"
      +]
  4. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / allow_external_path
      Added value: +{
      +  "default": false,
      +  "description": "true の場合のみ repo 内 exports/ 外への書き出しを許可する。",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / overwrite
      Added value: +{
      +  "default": false,
      +  "description": "true の場合のみ既存ファイルの上書きを許可する。",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / session_id / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}-\\d{6}$"New value: +"^\\d{4}-\\d{2}-\\d{2}-\\d{6}(?:-[0-9a-f]{8})?$"
  5. Changed5 schema fields changedv0.7.1
    • addedInput schema / properties / format / description
      Added value: +"出力形式。markdown は人間向け、json は完全な構造化ログ、csl-json は文献管理向け。"
    • addedInput schema / properties / include_unselected / description
      Added value: +"markdown/json の full_log で未選別候補を含めるかどうか。"
    • addedInput schema / properties / output_path / description
      Added value: +"出力先ファイルパス。未指定なら repo 内 exports/ に自動生成する。"
    • addedInput schema / properties / profile / description
      Added value: +"書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補。"
    • addedInput schema / properties / session_id / description
      Added value: +"書き出す過去セッションID。未指定なら現在の調査セッションを書き出す。"
  6. First observedv0.1.9

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the baseline is low, yet the description adds real context: the session is only read and never modified, output lands inside the server cwd exports/ unless output_path is given, and the default Markdown output is human-formatted. It does not restate the overwrite/external-path guards, but those are fully documented in the schema, so the gap is minor.

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 purpose statement is front-loaded in the opening phrase, followed by destination, format default, non-mutation guarantee, and the sibling redirect — each sentence carries distinct information. Slightly dense and mixing Japanese/English tokens, but no true filler.

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?

With an output schema present, return values need no explanation, and the input schema is fully annotated; the description covers purpose, default behavior, data-safety, and the alternative tool. What remains unstated (overwrite guard, external path guard) is already in the schema, so an agent can call this correctly.

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 description coverage is 100%, so all seven parameters are already documented in the schema, making 3 the baseline. The description reinforces only the default format and the output_path fallback; it adds no meaning for profile, overwrite, include_unselected, or allow_external_path beyond what the schema states.

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?

States a specific verb and resource ('export/write' a named investigation session to a file) and immediately scopes it via 'session_id で明示した調査セッション'. It also names the sibling it is NOT by pointing to jp_lit_export_view for cache/re-extraction output, so an agent can distinguish the two export tools without opening either schema.

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 gives the condition that selects the alternative: use jp_lit_export_view when only cache listings or re-extraction results should be written out. It also states the destination branches (exports/ under cwd vs. output_path) and the default format, so the agent knows when this tool is the right call and how it will behave by default.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.