argo-mcp

Create session summary mnemons

create_session_summary_mnemons

Create SessionSummary mnemons (structured summaries of game sessions). Players may not call this — GM/co-GM only.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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"
+}

Changed3 schema fields changedJun 3, 2026

removedInput schema / properties / items / items / properties / blocks

Removed value: -{
-  "description": "Initial content blocks (at least one).",
-  "items": {
-    "additionalProperties": false,
-    "description": "A single content block. Image blocks need assetId OR (data + mimeType).",
-    "properties": {
-      "assetId": {
-        "description": "Image block: pre-uploaded campaign asset id.",
-        "type": "string"
-      },
-      "caption": {
-        "description": "Image block caption.",
-        "type": "string"
-      },
-      "checked": {
-        "description": "Todo-block checked state.",
-        "type": "boolean"
-      },
-      "content": {
-        "description": "HTML text content for text-type blocks. Use <b>/<i>/<u>/<a>/<br>/<img> — NOT Markdown.",
-        "type": "string"
-      },
-      "data": {
-        "description": "Image block: inline base64 data (decoded server-side, max 5MB).",
-        "type": "string"
-      },
-      "filename": {
-        "description": "Image block filename hint.",
-        "type": "string"
-      },
-      "language": {
-        "description": "Code-block language hint.",
-        "type": "string"
-      },
-      "mimeType": {
-        "description": "Image block mime type — required when 'data' is set.",
-        "type": "string"
-      },
-      "type": {
-        "description": "Block type.",
-        "enum": [
-          "paragraph",
-          "heading1",
-          "heading2",
-          "bullet_list",
-          "numbered_list",
-          "todo",
-          "quote",
-          "code",
-          "callout",
-          "divider",
-          "image"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "type"
-    ],
-    "type": "object"
-  },
-  "minItems": 1,
-  "type": "array"
-}

addedInput schema / properties / items / items / properties / markdown

Added value: +{
+  "description": "Body content as Markdown. Mentions: @[label](mnemon:<entryId>). Images: ![caption](asset:<assetId>@<campaignId>) — upload the asset first.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / items / items / required

Previous value: -[
-  "title",
-  "blocks"
-]New value: +[
+  "title",
+  "markdown"
+]

First observedMay 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive intent, which the description aligns with. Beyond annotations, it discloses an access control requirement (GM/co-GM only), which is valuable behavioral context not present in the annotations. It doesn't describe side effects or output formats, but for a create tool this is acceptable given the annotations.

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, front-loaded sentence with no filler. It conveys the core purpose and a critical access restriction in just 13 words, making it exceptionally concise and well-structured.

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?

The tool has a complex input schema with a nested array of up to 50 items and many optional fields, but the description provides only a high-level purpose and access rule. It doesn't explain the overall payload structure or the intent of each field, and the schema itself does not describe top-level parameters. The description is insufficient for an agent to use the tool effectively without additional inference.

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

Parameters1/5

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

The description contains no information about the parameters (campaignId, items) or their meanings. With schema description coverage at 0% for top-level parameters, the description does nothing to explain how to construct a valid request, leaving the agent reliant entirely on the raw schema structure.

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 specifies a clear action ('Create') and a specific resource ('SessionSummary mnemons'), further clarified as 'structured summaries of game sessions.' This distinguishes it from sibling tools like create_archive_mnemons or create_quest_mnemons, and the GM-only restriction adds precise scope.

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?

The description clearly states who may use the tool ('GM/co-GM only') and implies that players should not call it, providing a strong contextual guideline. However, it does not explicitly mention when to use this over update_session_summary_mnemons or other create_*_mnemons tools, leaving some room for interpretation.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose. The mnemon tools are separated by type (NPC, Location, Quest, etc.), and other domains like guild, forum, and friend management are also well-segmented. No two tools appear to do the same thing.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern with snake_case. Some minor deviations: 'describe_mnemon_types' instead of 'list_mnemon_types', and 'invite_user_by_email' has a slightly different structure. Overall quite consistent.

Tool Count3/5

With 63 tools, the server is quite heavy. While each tool serves a specific purpose for campaign management, the sheer number may be overwhelming. It is borderline but still reasonable given the broad domain coverage.

Completeness4/5

The tool set covers CRUD for most resources (campaigns, sessions, mnemon types, guilds, friends, forum). Notable gaps: no delete_campaign or delete_session, and update_campaign is limited. However, the core workflows are well-covered.

Create session summary mnemons

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources