Skip to main content
Glama

add_event

Add events to your D&D adventure log to track combat, roleplay, exploration, quests, characters, world events, sessions, and social interactions with detailed descriptions and metadata.

Instructions

Add an event to the adventure log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYesType of event
descriptionYesEvent description
titleNoEvent title (optional, auto-generated from description if omitted)
session_numberNoSession number
characters_involvedNoCharacters involved — list or JSON array string, e.g. '["name1","name2"]'
locationNoLocation where event occurred
importanceNoEvent importance (1-5)
tagsNoTags for categorizing the event — list or JSON array string, e.g. '["npc","story"]'

Implementation Reference

  • The `add_event` method in `TimelineTracker` class adds a new event to the timeline, automatically assigning an ID if none exists, and then sorting the events chronologically.
    def add_event(self, event: TimelineEvent) -> str:
        """
        Add an event to the timeline.
    
        Events are automatically sorted chronologically after addition.
    
        Args:
            event: The event to add
    
        Returns:
            The event's ID (auto-generated if not provided)
        """
        if not event.id:
            event.id = f"evt_{uuid4().hex[:8]}"
        self._events.append(event)
        self._events.sort(key=lambda e: e.game_time._to_total_minutes())
        return event.id
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Add an event' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about permissions needed, whether this is idempotent, what happens on success/failure, or what the response contains. For a mutation tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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

Completeness2/5

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

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what constitutes a successful addition, what format the response takes, or any behavioral constraints. The description should provide more context about this write operation's implications and results.

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%, so the schema already documents all 8 parameters thoroughly. The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Add') and resource ('event to the adventure log'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'add_session_note' or 'add_death_save', which also add content to game logs.

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. With many sibling tools that also add content (like add_session_note, add_spell, add_item_to_character), there's no indication of when this specific event-logging tool is appropriate versus other addition 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/Polloinfilzato/dm20-protocol'

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