argo-mcp

Update NPC mnemons

update_npc_mnemons

Idempotent

Update typed/meta fields of NPC mnemons (visibility, tags, role, faction membership, etc.). An entry that is not an NPC fails its item; use update_faction_mnemons for a faction. Does NOT modify content blocks — use update_mnemons_content for that. Set visibility=PUBLIC on multiple NPCs in a single call by listing them in items[].

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

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.

Changed4 schema fields changedOct 18, 2026

addedInput schema / properties / items / items / properties / affiliationEntryIds / description
```
Added value: +"Factions this person belongs to (Faction entryIds or titles)."
```

removedInput schema / properties / items / items / properties / memberNpcEntryIds

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

removedInput schema / properties / items / items / properties / npcType

Removed value: -{
-  "enum": [
-    "FACTION",
-    "INDIVIDUAL"
-  ],
-  "type": "string"
-}

addedInput schema / properties / items / items / properties / role

Added value: +{
+  "description": "Free-text role or occupation. An empty string clears it.",
+  "type": "string"
+}

First observedMay 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-open-world behavior, so the bar is lower. The description still adds real context beyond them: per-item failure semantics for non-NPC entries, the content-vs-metadata boundary, and the batch nature of items[]. It stops short of describing result shape, but an output schema covers that.

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?

Four tight sentences, front-loaded with the core purpose and then the routing rules. Every sentence carries a distinct piece of actionable information with no filler.

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?

An output schema exists, so return values need not be explained. The description covers purpose, alternatives, failure semantics, and batching; the schema covers the max-50/items structure. Nothing an agent needs in order to invoke it correctly is missing.

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?

Top-level schema description coverage is 0%, so the description must carry weight. It names the salient editable fields (visibility, tags, role, faction membership), the visibility enum value PUBLIC, and the items[] batching construct. Some fields (sheetId, relationshipIds, primaryLocationEntryId, title) are only implied by 'etc.'

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 (Update) and resource (NPC mnemons' typed/meta fields), and enumerates the fields it touches. It explicitly separates itself from update_faction_mnemons and update_mnemons_content, so an agent can route correctly without opening sibling schemas.

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?

Gives explicit when-to-use and when-not-to-use: 'An entry that is not an NPC fails its item; use update_faction_mnemons for a faction' and 'Does NOT modify content blocks — use update_mnemons_content for that.' It also demonstrates a concrete batching use case (visibility=PUBLIC across multiple NPCs in one items[] call).

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.