Skip to main content
Glama

Chronicle

chronicle

Retrieve the fort's report stream as cursor-addressable events with stable IDs for incremental updates. Filter by category and collapse battle spam.

Instructions

The fort's announcement/report stream (combat, deaths, moods, artifacts, sieges, migrants, ...) as triaged, cursor-addressable events. Reads the rolling, front-pruned report window. Each event carries a stable id (monotonic and save/load-stable); pass the returned top-level cursor back as since to fetch only newer events (id > since). Omitting since returns the most recent limit events (default 50, max 200), oldest-to-newest. If since predates the retained window the response sets pruned:true (earlier events are gone — not silently omitted). Events are triaged into categories (death, birth, marriage, battle, siege, mood, artifact, migrants, diplomacy, cave-in, megabeast, other); filter with categories. Combat spam is tamed: repeat_count is honored, wrapped continuation lines fold into their event, and long consecutive battle runs collapse into a single marker (collapsed:true with collapsed_count) so one siege cannot flood the window — see battle_collapsed. Facts only: unit refs appear only when a report names a speaker (speaker_id != -1); combat reports carry no reliable unit, so they get a pos tile anchor instead. Returns {"error":"no fort loaded"} if no fort is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (default 50, capped at 200); newest are kept.
sinceNoCursor: return only events with id greater than this (from a prior `cursor`).
categoriesNoOptional subset of categories to return: death, birth, marriage, battle, siege, mood, artifact, migrants, diplomacy, cave-in, megabeast, other.
Behavior5/5

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

With no annotations provided, the description thoroughly discloses behavioral traits: the front-pruned window, stable ids, `pruned:true` flag, combat spam collapsing, and the rules about speaker_id and pos tile anchors. It even specifies the error response for no fort loaded, covering edge cases comprehensively.

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 dense but every sentence contributes necessary information. It is front-loaded with the core purpose, then logically progresses through cursor usage, defaults, pruning, categories, combat spam handling, facts, and error handling. There is no redundancy or filler, making it appropriately concise for its complexity.

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 complexity and lack of output schema, the description covers return semantics (cursor, pruned, collapsed), error handling, and parameter behavior. It preemptively answers likely questions about pagination, stale cursors, and combat-heavy stream summaries, making it contextually complete.

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

Parameters5/5

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

Although the schema already documents all parameters, the description adds significant context: default limit 50 and max 200, oldest-to-newest ordering, `since` semantics (id > since), and the pruned flag when `since` is stale. It also clarifies the `categories` filter with an exhaustive list of values.

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?

The description clearly identifies the tool as reading the fort's announcement/report stream and specifies the event types (combat, deaths, moods, artifacts, sieges, migrants). It distinguishes itself from sibling tools by focusing on this unique stream with triaged, cursor-addressable events.

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

Usage Guidelines4/5

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

It explains when to use the tool (to fetch announcements) and provides detailed usage instructions: passing `cursor` back as `since` for incremental fetches, omitting `since` for recent events, and using `categories` to filter. However, it does not explicitly mention when not to use it or compare it with alternatives, though the tool's unique scope makes this less critical.

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/alexanderolvera/dfhack-mcp'

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