Skip to main content
Glama

chronica_get_thread_info

Retrieve detailed information about a specific thread, including its content and metadata, from the Chronica memory server.

Instructions

指定されたスレッドの情報を取得します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesスレッドID

Implementation Reference

  • The handler implementation for the chronica_get_thread_info tool, which uses the store.get_thread_info method to retrieve thread details.
    elif name == "chronica_get_thread_info":
        thread_id = arguments.get("thread_id")
        
        if not thread_id:
            return [types.TextContent(
                type="text",
                text=json.dumps({"error": "validation_error", "message": "thread_id is required"}, ensure_ascii=False)
            )]
        
        thread_info = store.get_thread_info(thread_id)
        if thread_info:
            return [types.TextContent(
                type="text",
                text=json.dumps(thread_info, ensure_ascii=False, indent=2)
            )]
        else:
            return [types.TextContent(
                type="text",
                text=json.dumps({"error": "not_found", "message": f"Thread {thread_id} not found"}, ensure_ascii=False)
            )]
  • Tool definition and registration for chronica_get_thread_info within the list_tools function.
        name="chronica_get_thread_info",
        description="指定されたスレッドの情報を取得します。",
        inputSchema={
            "type": "object",
            "properties": {
                "thread_id": {
                    "type": "string",
                    "description": "スレッドID"
                }
            },
            "required": ["thread_id"]
        }
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only indicates a read operation via 'retrieves' but fails to mention error handling (e.g., thread not found), authentication requirements, or what specific 'information' is returned.

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 single-sentence description is appropriately sized for a simple tool with no wasted words. However, it lacks structural elements that could improve scannability, such as separating the action from return value notes.

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

Completeness3/5

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

While the input schema is fully described, the absence of annotations and output schema leaves significant gaps. The description does not compensate by explaining the return structure or thread 'info' contents, making it minimally viable but incomplete.

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%, establishing a baseline of 3. The description references '指定されたスレッド' (specified thread), which aligns with the thread_id parameter, but adds no additional semantic context such as ID format or where to obtain the ID.

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 uses a specific verb (取得します/retrieves) and resource (スレッドの情報/thread information), making the basic purpose clear. However, it does not explicitly differentiate from sibling tools like chronica_list_threads (which lists multiple threads) or chronica_create_thread.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., when to use get_thread_info vs list_threads), nor does it mention prerequisites such as obtaining a thread_id first.

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