argo-mcp

Update mnemon content

update_mnemons_content

Edit the body content of one or more mnemon entries. Each item carries an entryId and an ordered list of ops (append, insertAfter, replace, remove) applied atomically per entry. Op content is authored as Markdown (headings, lists, quotes, code fences, bold/italic, links) — do NOT send HTML. Mentions: @label. Images: caption — upload the asset first; inline base64 / data: URLs are not accepted. Node addressing: get body-node ids from get_mnemon, then target them in replace/remove/insertAfter. A single op's Markdown may produce several nodes; new nodes get fresh server-generated ids (replace keeps the original id on the first new node). On a bad op (missing blockId, unknown op, etc.) the whole entry's batch is rejected with the failedOpIndex; no partial mutation per entry. See describe_mnemon_types.blockOps for the full vocabulary.

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": {
      "campaignId": "<campaignId>",
      "items": "<items>"
    },
    "name": "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.

Changed13 schema fields changedJun 3, 2026

changedInput schema / properties / items / items / properties / ops / items / description

Previous value: -"A single block-level mutation. See describe_mnemon_types.blockOps."New value: +"A single body mutation, keyed by node id. See describe_mnemon_types.blockOps."

changedInput schema / properties / items / items / properties / ops / items / properties / afterBlockId / description

Previous value: -"Required for insertAfter."New value: +"Required for insertAfter: the body node id the new content follows."

removedInput schema / properties / items / items / properties / ops / items / properties / assetId
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / properties / items / items / properties / ops / items / properties / blockId / description

Previous value: -"Required for replace and remove."New value: +"Required for replace and remove: a body node id from get_mnemon."

removedInput schema / properties / items / items / properties / ops / items / properties / blockType

Removed value: -{
-  "description": "Required for append, insertAfter, replace.",
-  "enum": [
-    "paragraph",
-    "heading1",
-    "heading2",
-    "bullet_list",
-    "numbered_list",
-    "todo",
-    "quote",
-    "code",
-    "callout",
-    "divider",
-    "image"
-  ],
-  "type": "string"
-}

removedInput schema / properties / items / items / properties / ops / items / properties / caption
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / items / items / properties / ops / items / properties / checked
```
Removed value: -{
-  "type": "boolean"
-}
```
removedInput schema / properties / items / items / properties / ops / items / properties / data
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / items / items / properties / ops / items / properties / filename
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / items / items / properties / ops / items / properties / language
```
Removed value: -{
-  "type": "string"
-}
```

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

Added value: +{
+  "description": "Markdown content for append / insertAfter / replace. May produce several body nodes. Mentions: @[label](mnemon:<entryId>); images: ![caption](asset:<assetId>@<campaignId>).",
+  "type": "string"
+}

removedInput schema / properties / items / items / properties / ops / items / properties / mimeType
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / items / items / properties / ops / items / properties / text

Removed value: -{
-  "description": "HTML text for text-type blocks.",
-  "type": "string"
-}

First observedMay 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses atomicity per entry, full-batch rejection with failedOpIndex on bad ops, Markdown-only content (no HTML, no inline base64), and node-id addressing behavior. It also explains the multi-node production and id-keeping behavior for replace, adding substantial operational context.

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?

The description is long but information-dense; every sentence adds a needed technical constraint (Markdown vs HTML, image asset requirement, atomicity, error handling, id behavior). It is structured as a continuous paragraph, which is acceptable given the complexity, though a few bullet points could improve scannability.

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

Completeness5/5

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

Given the tool's complexity (nested arrays, 50-item limits, atomic ops, failure modes) and presence of an output schema, the description covers the essential behaviors: op semantics, ordering, node addressing, content syntax, asset handling, and rejection on bad ops. It even points to describe_mnemon_types.blockOps for full vocabulary, making it a thorough reference.

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?

The top-level parameters campaignId and items are not explicitly named in the description (0% schema description coverage), but it compensates by thoroughly explaining the nested item structure, entryId, the four op types, blockId, afterBlockId, and markdown format rules. The meaning of campaignId is left implicit, which is a minor gap given its simple schema definition.

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 opens with 'Edit the body content of one or more mnemon entries,' providing a specific verb and resource. It distinguishes itself from the many type-specific update_* siblings by focusing on ops-based content editing, and the detailed op list clarifies the unique scope.

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?

The description provides clear context on when and how to use the tool (editing body nodes via ops), and references get_mnemon for node IDs and describe_mnemon_types for op vocabulary. However, it never explicitly contrasts this tool with the many sibling update_* tools (e.g., update_custom_mnemons), leaving the choice only implied.

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

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.