Skip to main content
Glama

jp_lit_list_sessions

List past research sessions sorted by update or creation date, with filters for trace presence, selected candidates, source, and date range. Find sessions to resume when search terms are forgotten.

Instructions

read-only。過去の調査セッションを新しい順または作成日順に一覧し、trace や選別済み候補の有無、source、日付範囲で絞り込む。検索語を覚えていない調査履歴の棚卸しや再開候補探しに使う。特定語で探す場合は jp_lit_find_sessions を使う。session や cache は変更しない

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo返すセッション件数。最大 100。
sourceNo結果を特定 source に絞る。未指定の場合は tool ごとの既定動作に従う。
sort_byNoセッション一覧の並び替え項目。updated_at
has_traceNo調査目的・source plan・次アクションなど trace を持つセッションだけに絞る。
created_toNocreated_at の上限 ISO datetime。
sort_orderNoセッション一覧の並び順。desc は新しい順。desc
updated_toNoupdated_at の上限 ISO datetime。
created_fromNocreated_at の下限 ISO datetime。
has_selectedNo選別済み候補を持つセッションだけに絞る。
updated_fromNoupdated_at の下限 ISO datetime。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
filtersYes
sort_byYes
sort_orderYes
Behavior4/5

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

The description states 'read-only' and 'does not change sessions or cache', covering the non-destructive nature. With no annotations, it provides key behavioral info, though more details on pagination or limits could be added.

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, front-loaded with 'read-only', and every sentence adds value without redundancy.

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 (10 parameters, many siblings), the description covers purpose, usage, alternative, and safety. Output schema exists, so return details are unnecessary.

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 the schema already describes each parameter. The description adds only a brief overview, not much additional meaning beyond the schema.

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 lists past sessions with ordering and filtering options, and explicitly distinguishes from sibling jp_lit_find_sessions for term-based search.

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?

It explicitly says when to use (inventory of history, resume candidates) and when not to use (specific term search, use jp_lit_find_sessions).

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