Skip to main content
Glama

Campaign overview

dos2_campaign
Read-onlyIdempotent

Reads one Divinity: Original Sin 2 campaign and returns a read-only overview of metadata, mods, scenes, maps, pins, vignettes, templates, notes, and journal to orient before editing.

Instructions

Reads one campaign and returns a compact overview: metadata and attached add-on mods, scenes, Overview maps with their pins, vignettes (uuid, title, answers), NPC and item templates (kind, name, level), sticky notes (title, kind, folder) and the whole journal.

Read-only. Use it to orient yourself before reading details or editing. For full content follow up with
dos2_scene (who stands in a scene), dos2_template (one template), dos2_vignettes or dos2_notes. To pick a
campaign in the first place use dos2_status.

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": {
      "campaign": "<campaign>"
    },
    "name": "dos2_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignYesThe campaign to work on: its name, its folder name, its UUID, or a unique part of any of them. dos2_status lists the campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / campaign / description
      Added value: +"The campaign to work on: its name, its folder name, its UUID, or a unique part of any of them. dos2_status lists the campaigns."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' itself is largely redundant. What the description does add is crucial behavioral context absent from annotations: the result is a *compact* overview rather than full content, with an itemized list of exactly which fields each section carries (e.g. vignettes by uuid/title/answers, notes by title/kind/folder), which tells the agent to expect summaries and follow up elsewhere for detail.

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?

Front-loaded with the action and the returned payload, then a short second paragraph for routing. Structure is clean and scannable. Minor waste: 'Read-only' restates the annotations, and the parenthetical field lists are dense but each one earns its place by defining the 'compact' contract.

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?

With no output schema, the description must describe returns — and it does so thoroughly, including that the *whole* journal is returned. The remaining gap is scale/behavior on large campaigns: nothing warns that a full journal or many scenes could produce a very large response or how that is bounded. Otherwise complete for a one-parameter read tool with rich annotations.

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%, and the schema already explains that the campaign parameter accepts a name, folder name, UUID, or unique fragment and that dos2_status lists campaigns. The description adds no additional semantics (no ambiguity resolution rules, no case-insensitivity note) beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource ('Reads one campaign') and immediately enumerates what the overview contains: metadata, add-on mods, scenes, Overview maps and pins, vignettes, templates, sticky notes and journal. This is precise enough to distinguish it from siblings like dos2_campaign_meta or dos2_scene without opening any schema.

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

Usage Guidelines5/5

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

Explicit orientation guidance is given ('Use it to orient yourself before reading details or editing'), plus a concrete follow-up routing table: dos2_scene for scene contents, dos2_template for one template, dos2_vignettes, dos2_notes, and dos2_status for picking a campaign. When-to-use, when-to-escalate, and the entry-point dependency are all named.

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