Skip to main content
Glama

jp_lit_list_sessions

List past research sessions sorted by newest to review forgotten search histories and find sessions to resume.

Instructions

過去の調査セッションを新しい順に一覧する。検索語を覚えていない調査履歴の棚卸しや再開候補探しに使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
updated_fromNo
updated_toNo
created_fromNo
created_toNo
has_traceNo
has_selectedNo
sourceNo
sort_byNoupdated_at
sort_orderNodesc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYes
totalYes
sort_byYes
sort_orderYes
filtersYes
itemsYes

Implementation Reference

  • The main handler function that lists all sessions, filters by criteria (updated_at, created_at, has_trace, has_selected, source), sorts, limits, and returns structured output.
    export function createJpLitListSessionsTool(sessionStore: SessionStore) {
      return async (input: unknown) => {
        const parsed = listSessionsInputSchema.parse(input);
        const sessions = await sessionStore.listAll();
    
        const items = sessions
          .map((session) => {
            const sources = collectSources(session);
            const selectedCount = countSelectedItems(session);
            const traceCounts = getTraceCounts(session);
            const sessionHasTrace = hasTrace(session);
            const sessionHasSelected = selectedCount > 0;
    
            return {
              session_id: session.session_id,
              created_at: session.created_at,
              updated_at: session.updated_at,
              research_goal: session.trace?.research_goal ?? null,
              scope_note: session.trace?.scope_note ?? null,
              entry_count: session.entries.length,
              selected_count: selectedCount,
              source_count: sources.length,
              sources,
              query_preview: pickQueryPreview(session),
              selected_title_preview: pickSelectedTitlePreview(session),
              has_trace: sessionHasTrace,
              has_selected: sessionHasSelected,
              trace_counts: traceCounts
            };
          })
          .filter((item) =>
            isAfterOrEqual(item.updated_at, parsed.updated_from) &&
            isBeforeOrEqual(item.updated_at, parsed.updated_to) &&
            isAfterOrEqual(item.created_at, parsed.created_from) &&
            isBeforeOrEqual(item.created_at, parsed.created_to) &&
            (parsed.has_trace === undefined || item.has_trace === parsed.has_trace) &&
            (parsed.has_selected === undefined || item.has_selected === parsed.has_selected) &&
            (parsed.source === undefined || item.sources.includes(parsed.source))
          )
          .sort((left, right) => {
            const comparison = left[parsed.sort_by].localeCompare(right[parsed.sort_by]);
            return parsed.sort_order === "asc" ? comparison : -comparison;
          });
    
        const structuredContent: ListSessionsOutput = listSessionsOutputSchema.parse({
          limit: parsed.limit,
          total: items.length,
          sort_by: parsed.sort_by,
          sort_order: parsed.sort_order,
          filters: {
            updated_from: parsed.updated_from ?? null,
            updated_to: parsed.updated_to ?? null,
            created_from: parsed.created_from ?? null,
            created_to: parsed.created_to ?? null,
            has_trace: parsed.has_trace ?? null,
            has_selected: parsed.has_selected ?? null,
            source: parsed.source ?? null
          },
          items: items.slice(0, parsed.limit)
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(structuredContent, null, 2)
            }
          ],
          structuredContent
        };
      };
    }
  • Helper functions used by the handler: createPreview, countSelectedItems, collectSources, pickQueryPreview, pickSelectedTitlePreview, getTraceCounts, hasTrace, isAfterOrEqual, isBeforeOrEqual.
    function createPreview(value: string | null | undefined, maxLength = 120) {
      if (!value) {
        return null;
      }
    
      const compact = value.replace(/\s+/g, " ").trim();
      if (compact.length <= maxLength) {
        return compact;
      }
    
      return `${compact.slice(0, maxLength - 1)}…`;
    }
    
    function countSelectedItems(session: SessionDocument) {
      return session.entries.reduce(
        (count, entry) => count + entry.selected_items.length,
        0
      );
    }
    
    function collectSources(session: SessionDocument) {
      const sources = new Set<Source>();
      const addSource = (value: unknown) => {
        const parsed = sourceSchema.safeParse(value);
        if (parsed.success) {
          sources.add(parsed.data);
        }
      };
    
      for (const entry of session.entries) {
        addSource(entry.input.source);
        for (const item of entry.selected_items) {
          addSource(item.source);
        }
      }
    
      for (const plan of session.trace?.source_plans ?? []) {
        addSource(plan.source);
      }
      for (const action of session.trace?.next_actions ?? []) {
        addSource(action.source);
      }
    
      return Array.from(sources).sort();
    }
    
    function pickQueryPreview(session: SessionDocument) {
      for (const entry of session.entries) {
        const query = entry.input.query;
        if (typeof query === "string") {
          return createPreview(query);
        }
      }
    
      return null;
    }
    
    function pickSelectedTitlePreview(session: SessionDocument) {
      for (const entry of session.entries) {
        const title = entry.selected_items[0]?.title;
        if (title) {
          return createPreview(title);
        }
      }
    
      return null;
    }
    
    function getTraceCounts(session: SessionDocument) {
      return {
        source_plan_count: session.trace?.source_plans.length ?? 0,
        open_question_count: session.trace?.open_questions.length ?? 0,
        next_action_count: session.trace?.next_actions.length ?? 0,
        decision_count: session.entries.reduce(
          (count, entry) => count + (entry.trace?.decisions.length ?? 0),
          0
        ),
        evidence_scope_count: session.entries.reduce(
          (count, entry) => count + (entry.trace?.evidence_scope.length ?? 0),
          0
        )
      };
    }
    
    function hasTrace(session: SessionDocument) {
      const counts = getTraceCounts(session);
      return Boolean(
        session.trace?.research_goal ||
          session.trace?.scope_note ||
          counts.source_plan_count > 0 ||
          counts.open_question_count > 0 ||
          counts.next_action_count > 0 ||
          counts.decision_count > 0 ||
          counts.evidence_scope_count > 0 ||
          session.entries.some((entry) => entry.trace?.intent || entry.trace?.search_attempt)
      );
    }
    
    function isAfterOrEqual(value: string, lowerBound?: string) {
      return lowerBound === undefined || value >= lowerBound;
    }
    
    function isBeforeOrEqual(value: string, upperBound?: string) {
      return upperBound === undefined || value <= upperBound;
    }
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It confirms a read-only list operation but omits details about pagination, filtering defaults, or potential side effects, which are partially captured in the schema.

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?

Two concise sentences front-load the primary action, but the extreme brevity sacrifices parameter guidance, which is critical for this complex schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description omits essential context for filtering, sorting, and limit behavior, making it inadequate for a 10-parameter tool with no parameter descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 10 parameters, the description provides no parameter explanations, leaving the agent to infer meaning from schema structure alone, which is insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists past sessions in newest order, distinguishing itself from sibling search tools by focusing on inventory and resumption. However, it could more explicitly differentiate from jp_lit_find_sessions.

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

Usage Guidelines3/5

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

Provides context for when to use (inventory, resumption candidates) but lacks explicit when-not-to-use or alternative tools, leaving some ambiguity.

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