Skip to main content
Glama

chronica_get_last_seen

Retrieve the last seen timestamp for specified thread types to track recent activity and maintain context across sessions.

Instructions

指定されたスレッドタイプで最後に見た時刻を取得します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_typeYesスレッドタイプ(必須)

Implementation Reference

  • The handler implementation for the chronica_get_last_seen tool, which validates arguments and calls the store to get the last seen time.
    elif name == "chronica_get_last_seen":
        thread_type = arguments.get("thread_type")
        if not thread_type:
            return [types.TextContent(
                type="text",
                text=json.dumps({"error": "invalid_thread", "message": "thread_type is required"}, ensure_ascii=False)
            )]
        
        if thread_type not in ["normal", "project"]:
            return [types.TextContent(
                type="text",
                text=json.dumps({"error": "invalid_thread", "message": f"thread_type must be 'normal' or 'project', got: {thread_type}"}, ensure_ascii=False)
            )]
        
        last_seen_time = store.get_last_seen(thread_type)
        result = {"last_seen_time": last_seen_time} if last_seen_time else {"last_seen_time": None}
        return [types.TextContent(
            type="text",
            text=json.dumps(result, ensure_ascii=False)
        )]
  • The schema definition for the chronica_get_last_seen tool.
    inputSchema={
        "type": "object",
        "properties": {
            "thread_type": {
                "type": "string",
                "enum": ["normal", "project"],
                "description": "スレッドタイプ(必須)"
            }
        },
        "required": ["thread_type"]
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to specify the timestamp format (ISO 8601, Unix epoch, etc.), return value when no 'last seen' exists (null vs zero), or whether this operation has side effects like updating session state.

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 description is a single, efficient sentence with no wasted words. The main verb appears early, making it front-loaded. However, given the lack of annotations and output schema, extreme brevity here results in under-specification rather than optimal conciseness.

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?

For a single-parameter read operation, the description adequately identifies the function but lacks critical context given the absence of an output schema. It omits the return value structure, timestamp format, and error handling behavior (e.g., invalid thread_type), leaving clear gaps in completeness.

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% (the parameter 'thread_type' is documented in the schema as 'スレッドタイプ(必須)'). The description references '指定されたスレッドタイプ' which aligns with the schema, adding no substantial semantic meaning beyond the schema's documentation, meeting the baseline for high-coverage schemas.

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 (取得します/gets) and resource (最後に見た時刻/last seen timestamp) with clear scope (指定されたスレッドタイプ/specified thread type). However, it does not explicitly differentiate from the sibling tool 'chronica_get_thread_info', which could also retrieve thread metadata.

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?

No guidance provided on when to use this tool versus alternatives like 'chronica_get_thread_info' or 'chronica_list_threads'. The description states what it does but not the specific scenario or prerequisite conditions for selecting it.

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