argo-mcp

Update session summary mnemons

update_session_summary_mnemons

Idempotent

Update the recap, date, number and meta fields of SessionSummary mnemons. To change the story, use update_mnemons_content.

Input Schema

Name	Required	Description	Default
`items`	Yes
`campaignId`	Yes

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 23, 2026

removedInput schema / properties / items / items / properties / combats

Removed value: -{
-  "description": "Combat encounters that took place this session.",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "description": {
-        "description": "Who fought whom and where, in one sentence.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "outcome": {
-        "description": "How it resolved, e.g. \"party victorious, no casualties\".",
-        "type": "string"
-      }
-    },
-    "required": [
-      "description"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / items / items / properties / date / description

Added value: +"When the session was played: ISO date (2024-02-10) or date-time. Set it for a past chapter brought into Argo. Leave it out for a summary linked to a calendar session: it then takes the session's date. Linking never clears it. An empty string clears it."

removedInput schema / properties / items / items / properties / detailedSummary

Removed value: -{
-  "description": "Full narrative summary, 3-5 paragraphs.",
-  "type": "string"
-}

removedInput schema / properties / items / items / properties / loot

Removed value: -{
-  "description": "Items, treasure, or rewards acquired.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / majorEvents

Removed value: -{
-  "description": "Significant story beats, in chronological order.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / npcsMentioned

Removed value: -{
-  "description": "NPCs that appeared or were referenced. This is descriptive only — to link one to an existing NPC mnemon, call create_mnemon_relationship with SESSION_ATTENDEE_NPC.",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "name": {
-        "description": "Name as referenced in the session, e.g. \"Captain Mira\".",
-        "minLength": 1,
-        "type": "string"
-      },
-      "role": {
-        "description": "Role played this session, e.g. \"quest-giver\", \"rescued captive\".",
-        "type": "string"
-      }
-    },
-    "required": [
-      "name"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / oneSentenceSummary

Removed value: -{
-  "description": "Single-sentence TL;DR of what happened.",
-  "type": "string"
-}

removedInput schema / properties / items / items / properties / openThreads

Removed value: -{
-  "description": "Unresolved threads and cliffhangers as of session end.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / partyDecisions

Removed value: -{
-  "description": "Meaningful choices that will shape future sessions.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / partyEndState

Removed value: -{
-  "additionalProperties": {
-    "type": "string"
-  },
-  "description": "Character display name -> short end-of-session status line.",
-  "type": "object"
-}

removedInput schema / properties / items / items / properties / previouslyOn

Removed value: -{
-  "description": "Where each player ended — read aloud at the top of the next session.",
-  "type": "string"
-}

addedInput schema / properties / items / items / properties / recap

Added value: +{
+  "description": "Short recap, 1-3 sentences, ending on where the party stands. Shown as \"Previously on\" on the next session and the campaign Dashboard. The full story goes in the Markdown body.",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / sessionNumber / description

Added value: +"The session's number in the party's history, a positive whole number, kept as written. Leave it out to let Argo number the summary by its place in the history (after the highest number before it). Linking never clears it. 0 clears it."

removedInput schema / properties / items / items / properties / suggestedTitle

Removed value: -{
-  "description": "Short evocative title for the session, like a TV episode title.",
-  "type": "string"
-}

Changed15 schema fields changedJul 21, 2026

removedInput schema / properties / items / items / properties / attendeeCharacterIds

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / items / items / properties / attendeeNpcEntryIds

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / items / items / properties / combats

Added value: +{
+  "description": "Combat encounters that took place this session.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "description": "Who fought whom and where, in one sentence.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "outcome": {
+        "description": "How it resolved, e.g. \"party victorious, no casualties\".",
+        "type": "string"
+      }
+    },
+    "required": [
+      "description"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / detailedSummary

Added value: +{
+  "description": "Full narrative summary, 3-5 paragraphs.",
+  "type": "string"
+}

removedInput schema / properties / items / items / properties / linkedLocationEntryIds
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```

removedInput schema / properties / items / items / properties / linkedQuestEntryIds

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / items / items / properties / loot

Added value: +{
+  "description": "Items, treasure, or rewards acquired.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / majorEvents

Added value: +{
+  "description": "Significant story beats, in chronological order.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / npcsMentioned

Added value: +{
+  "description": "NPCs that appeared or were referenced. This is descriptive only — to link one to an existing NPC mnemon, call create_mnemon_relationship with SESSION_ATTENDEE_NPC.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "Name as referenced in the session, e.g. \"Captain Mira\".",
+        "minLength": 1,
+        "type": "string"
+      },
+      "role": {
+        "description": "Role played this session, e.g. \"quest-giver\", \"rescued captive\".",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / oneSentenceSummary

Added value: +{
+  "description": "Single-sentence TL;DR of what happened.",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / openThreads

Added value: +{
+  "description": "Unresolved threads and cliffhangers as of session end.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / partyDecisions

Added value: +{
+  "description": "Meaningful choices that will shape future sessions.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / partyEndState

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Character display name -> short end-of-session status line.",
+  "type": "object"
+}

addedInput schema / properties / items / items / properties / previouslyOn

Added value: +{
+  "description": "Where each player ended — read aloud at the top of the next session.",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / suggestedTitle

Added value: +{
+  "description": "Short evocative title for the session, like a TV episode title.",
+  "type": "string"
+}

First observedMay 14, 2026

TDQS

A4/5.0

Behavior3/5

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

The annotations already declare a non-destructive, idempotent mutation. The description adds a useful behavioral boundary that only recap, date, number, and meta fields are changed, while story content belongs elsewhere. It does not explain permissions, failure behavior, or precisely what "meta fields" includes.

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 short sentences, front-loaded with the core action and followed by the key sibling routing instruction. There is no wasted text.

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?

The output schema and detailed nested property descriptions mean the description need not explain return values or every field. It is largely complete for selection and invocation, though it could mention the batch-item structure and required campaign context.

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?

The schema itself richly documents date, recap, entryId, and sessionNumber, but the description only lists "recap, date, number and meta fields" and says nothing about the required items array, campaignId, or the 50-item batch limit. It adds the story-vs-recap distinction, but does not fully compensate for the top-level 0% schema description coverage.

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 states a specific verb and resource: update SessionSummary mnemons. It enumerates the updated fields (recap, date, number, meta) and explicitly distinguishes this from update_mnemons_content for story changes. An agent can identify the tool without opening the schema.

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 explicitly routes story-content changes to update_mnemons_content, which is the key sibling alternative. The usage context is clear, though it does not spell out broader when-not conditions or prerequisites.

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

All argo-mcp tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.