Skip to main content
Glama

create_person_timeline_note

Add timeline notes to a person's record in LunaTask, associating information with specific dates for tracking history and context.

Instructions

Create a timeline note for a person in LunaTask. Requires person_id and content. Optional date_on (YYYY-MM-DD) to associate the note with a specific day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idYes
contentYes
date_onNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the "create_person_timeline_note" tool logic.
    async def create_person_timeline_note_tool(
        self,
        ctx: ServerContext,
        person_id: str,
        content: str,
        date_on: str | None = None,
    ) -> dict[str, Any]:
        """Create a timeline note for a person in LunaTask.
    
        Args:
            ctx: Server context for logging and communication
            person_id: ID of the person to add the timeline note to
            content: Content of the timeline note
            date_on: Optional date in YYYY-MM-DD format to associate with the note
    
        Returns:
            Dictionary with success status, person_timeline_note_id, and message.
        """
    
        await ctx.info("Creating person timeline note")
    
        if not person_id.strip():
            message = "person_id is required to create a timeline note"
            await ctx.error(message)
            logger.warning("Missing person_id for person timeline note creation")
            return {
                "success": False,
                "error": "validation_error",
                "message": message,
            }
    
        if content.strip() == "":
            message = "content cannot be empty when creating a timeline note"
            await ctx.error(message)
            logger.warning("Empty content provided for person timeline note creation")
            return {
                "success": False,
                "error": "validation_error",
                "message": message,
            }
    
        parsed_date: date_class | None = None
        if date_on is not None:
            try:
                parsed_date = date_class.fromisoformat(date_on)
            except ValueError as error:
                message = f"Invalid date_on format. Expected YYYY-MM-DD format: {error!s}"
                await ctx.error(message)
                logger.warning("Invalid date_on provided for person timeline note: %s", date_on)
                return {
                    "success": False,
                    "error": "validation_error",
                    "message": message,
                }
    
        note_payload = PersonTimelineNoteCreate(
            person_id=person_id,
            content=content.strip(),
            date_on=parsed_date,
        )
    
        try:
            async with self.lunatask_client as client:
                note_response = await client.create_person_timeline_note(note_payload)
    
        except Exception as error:
            return await self._handle_lunatask_api_errors(ctx, error, "timeline note creation")
    
        await ctx.info(f"Person timeline note created: {note_response.id}")
        logger.info("Created person timeline note %s", note_response.id)
        return {
            "success": True,
            "person_timeline_note_id": note_response.id,
            "message": "Person timeline note created successfully",
        }
  • Tool registration for "create_person_timeline_note".
    async def _create_person_timeline_note(
        ctx: ServerContext,
        person_id: str,
        content: str,
        date_on: str | None = None,
    ) -> dict[str, Any]:
        return await self.create_person_timeline_note_tool(ctx, person_id, content, date_on)
    
    self.mcp.tool(
        name="create_person_timeline_note",
        description=(
            "Create a timeline note for a person in LunaTask. Requires person_id and content. "
            "Optional date_on (YYYY-MM-DD) to associate the note with a specific day."
        ),
    )(_create_person_timeline_note)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It identifies this as a creation operation but doesn't mention permission requirements, whether the note is editable/deletable, rate limits, or what happens on success/failure. The description adds minimal behavioral context beyond the basic creation action.

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 efficiently structured in two sentences: the first states the purpose and requirements, the second explains the optional parameter. Every word serves a purpose with zero wasted text, making it easy to parse quickly.

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?

Given this is a creation tool with no annotations but with an output schema (which handles return values), the description covers the basic operation and parameters adequately. However, for a mutation tool that creates persistent data, it should ideally mention permission requirements or side effects that aren't covered by the output schema.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by explaining all three parameters: person_id and content as required, and date_on as optional with format specification (YYYY-MM-DD). This adds meaningful context beyond what the bare schema provides, though it doesn't explain what 'person_id' refers to or constraints on 'content'.

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 the action ('Create a timeline note') and resource ('for a person in LunaTask'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_note' or 'create_journal_entry', which likely create different types of notes in the same system.

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?

The description implies usage context by specifying required parameters (person_id and content) and mentioning the optional date_on parameter. However, it provides no explicit guidance about when to use this tool versus alternatives like 'create_note' or 'create_journal_entry', nor does it mention prerequisites or exclusions.

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/tensorfreitas/lunatask-mcp'

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