Skip to main content
Glama

chronica_list_threads

Retrieve a list of memory threads with names, IDs, entry counts, and dates from the Chronica MCP server to organize and access structured memory across sessions.

Instructions

スレッド一覧を取得します(スレッド名・ID・エントリ件数・日付のみ)。 エントリの本文やタグは含まれない。記憶の中身を見せる・列挙するには chronica_search を使う(引数なしで直近の記憶一覧)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_typeNoスレッドタイプでフィルタ(省略時は全て)

Implementation Reference

  • Implementation of the 'chronica_list_threads' tool handler, which calls the store's list_threads method.
    elif name == "chronica_list_threads":
        thread_type = arguments.get("thread_type")
        threads = store.list_threads(thread_type=thread_type)
        return [types.TextContent(
            type="text",
            text=json.dumps({"threads": threads}, ensure_ascii=False, indent=2)
        )]
  • Tool registration for 'chronica_list_threads' including its input schema and description.
                    name="chronica_list_threads",
                    description="""
    スレッド一覧を取得します(スレッド名・ID・エントリ件数・日付のみ)。
    エントリの本文やタグは含まれない。記憶の中身を見せる・列挙するには chronica_search を使う(引数なしで直近の記憶一覧)。
    """,
                    inputSchema={
                        "type": "object",
                        "properties": {
                            "thread_type": {
                                "type": "string",
                                "enum": ["normal", "project"],
                                "description": "スレッドタイプでフィルタ(省略時は全て)"
                            }
                        }
                    }
                ),
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly discloses data scope boundaries (what is returned vs what is excluded: 'エントリの本文やタグは含まれない'), setting accurate expectations. Could improve by mentioning pagination or empty result handling, but the inclusion/exclusion disclosure is the critical behavioral info for this list operation.

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?

Two sentences with zero waste. First sentence establishes operation and return fields; second sentence clarifies exclusions and names specific alternative tool. Information is front-loaded and density is optimal for quick agent comprehension.

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 tool's simplicity (1 optional parameter, no output schema), the description is complete. It compensates for missing output schema by enumerating returned fields, clarifies the tool's position in the toolbox relative to chronica_search, and provides sufficient context for an agent to invoke 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 has 100% description coverage (thread_type parameter fully documented as optional filter). Description focuses on output semantics rather than repeating parameter details, which is appropriate when schema is self-documenting. Baseline 3 is correct for high schema coverage without additional parameter guidance in description.

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?

Description uses specific verb '取得します' (retrieves) with clear resource scope 'スレッド名・ID・エントリ件数・日付のみ' (name, ID, count, date only). It explicitly distinguishes from sibling tool chronica_search by contrasting shallow thread listing vs deep memory content enumeration.

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?

Provides explicit when-not guidance: '記憶の中身を見せる・列挙するには chronica_search を使う' (use chronica_search to show/enumerate memory contents). It even includes usage hint for the alternative (no arguments for recent memories), giving clear selection criteria between tools.

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/Nic9dev/Chronica'

If you have feedback or need assistance with the MCP directory API, please join our Discord server