legendsviewer-mcp

Read one object

read_object

Get the history of any Dwarf Fortress world object as prose. Choose digest mode to condense large objects into event summaries and rare occurrences; full mode returns complete details.

Instructions

The history of a single world object as prose. detail='digest' condenses it to the event type breakdown, an activity histogram and only the events whose type is rare for that object — use it for civilizations and other large objects, whose full dossier can exceed 600 KB. detail='full' returns everything.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "read_object"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Object id.
`type`	Yes	Object type, for example "HistoricalFigure", "Entity", "Site", "War".
`detail`	No	How much to return.	digest
`toYear`	No	Latest year, inclusive.
`fromYear`	No	Earliest year, inclusive.
`maxEvents`	No	Cap on events (full) or on notable events (digest). 0 means no limit.
`eventTypes`	No	Comma separated raw event type names, exactly as printed in brackets on each event line (for example "hf died,created site"). Narrowing here also makes event search far faster.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses meaningful behavioral details: the digest mode returns an event type breakdown, activity histogram, and only rare events, and warns that full dossiers can exceed 600 KB. This goes beyond a basic read operation, though it does not mention all limits or output structure.

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?

Two tight sentences: the first states the core purpose, the second explains the detail modes and use cases. No waste, no redundancy, and the most important information is front-loaded.

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

Completeness4/5

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

For a 7-parameter tool with no output schema, the description explains the primary behavior and the digest/full distinction well. It does not illustrate how filtering parameters (toYear, fromYear, maxEvents, eventTypes) combine, but the schema covers their meanings, so this is adequate.

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?

Schema coverage is 100%, so the baseline is 3. The description adds semantic value to the 'detail' parameter by explaining what digest vs full actually produce and when to use each, exceeding baseline.

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 tool reads the history of a single world object as prose, with a specific verb and resource. It implicitly contrasts with siblings like search_objects (which searches), but does not explicitly name alternatives.

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?

It gives clear guidance on when to use 'digest' vs 'full' based on object size, which is useful context. However, it does not explain when to choose this tool over siblings like search_objects or world_summary, nor does it provide any exclusions or alternative tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server