Skip to main content
Glama

argo-mcp

by io.github.Argo-RPG-Platform
OverviewDiscussionsAdmin

Update session summary mnemons

update_session_summary_mnemons
Idempotent

Update typed/meta fields of SessionSummary mnemons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
campaignIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • 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"
+}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already indicate it is a write operation (readOnlyHint=false), non-destructive (destructiveHint=false), and idempotent (idempotentHint=true). The description adds no extra behavioral context such as whether updates merge or replace fields, or what 'typed/meta fields' means operationally.

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?

A single sentence that is front-loaded with the verb and resource. No wasted words or irrelevant details.

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 schema with nested objects and many fields, plus many sibling tools, but the description is minimal. It does not explain the difference from 'update_mnemons_content', the semantics of partial updates, or the meaning of 'typed/meta'. The output schema exists, but operational completeness is lacking.

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

Parameters2/5

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

The description provides no parameter information. Schema description coverage is 0%, and the description does not compensate by explaining 'campaignId' (which lacks a schema description) or the structure of 'items'. Though the nested schema has rich descriptions for properties, the key top-level params remain unexplained.

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 states a specific verb ('Update') and resource ('SessionSummary mnemons'), and narrows the scope to 'typed/meta fields'. This distinguishes it from generic content updates, though it does not explicitly contrast with siblings like 'update_mnemons_content'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'update_mnemons_content' or 'create_session_summary_mnemons'. The description only states what it does, not when it should be chosen.

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

All argo-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources