argo-mcp

Get mnemon

get_mnemon

Read-onlyIdempotent

Get the full details of a specific mnemon entry (title, blocks, type properties). For a quest, quest holds its status, kind, playersCanTick, objectives and reward chips (with their ids), progress and reward totals, as the current user may see them — read objectives and rewards there, not from blocks.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entryId`	Yes	Mnemon entry ID (hex) or exact title.
`campaignId`	Yes	Campaign ID.

Output Schema

TableJSON Schema

Name	Required	Description
`type`	Yes
`quest`	No	Quests only: status, kind, objectives, reward chips and progress as this user may see them.
`title`	Yes
`blocks`	Yes
`entryId`	Yes
`typeProperties`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedOutput schema / properties / quest

Added value: +{
+  "additionalProperties": false,
+  "description": "Quests only: status, kind, objectives, reward chips and progress as this user may see them.",
+  "properties": {
+    "kind": {
+      "description": "Main | Side | Personal.",
+      "type": "string"
+    },
+    "objectives": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "depth": {
+            "description": "0 for a top-level objective.",
+            "type": "number"
+          },
+          "hidden": {
+            "description": "GM reads only: true when players cannot see it.",
+            "type": "boolean"
+          },
+          "id": {
+            "description": "Name it in set_quest_objective_state or update_quest_mnemons.",
+            "type": "string"
+          },
+          "optional": {
+            "type": "boolean"
+          },
+          "parentId": {
+            "type": "string"
+          },
+          "state": {
+            "description": "open | done | failed.",
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "text",
+          "state",
+          "optional",
+          "depth"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "playersCanTick": {
+      "type": "boolean"
+    },
+    "progress": {
+      "additionalProperties": false,
+      "description": "Required objectives done of those this user can see; optional and failed ones do not count.",
+      "properties": {
+        "done": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "done",
+        "total"
+      ],
+      "type": "object"
+    },
+    "rewardTotals": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "amount": {
+                "type": "number"
+              },
+              "unit": {
+                "type": "string"
+              },
+              "unitLabel": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "xp": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "currency"
+      ],
+      "type": "object"
+    },
+    "rewards": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "entryId": {
+            "type": "string"
+          },
+          "hidden": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "description": "currency | xp | item | other.",
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "ruleEntryId": {
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          },
+          "unitLabel": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "kind"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Available | Active | Completed | Failed.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "kind",
+    "playersCanTick"
+  ],
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and non-open-world traits. The description adds valuable behavioral context: it enumerates what data is returned and notes user-dependent visibility ('as the current user may see them'), which goes beyond the annotations without contradicting them.

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 sentences with no wasted words. The main purpose is front-loaded, and the second sentence efficiently adds quest-specific detail without redundancy.

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 simple two-parameter schema, rich annotations, and the presence of an output schema, the description provides all necessary context: what the tool returns, how quest data is structured, and user visibility. Nothing critical is missing for correct invocation.

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?

Schema description coverage is 100%, so the schema fully documents the two required parameters. The description does not add any parameter-level information beyond what the schema provides, so the baseline score of 3 applies.

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 clearly states a specific verb (Get) and resource (full details of a specific mnemon entry) and distinguishes itself from list/search siblings by emphasizing 'specific' and 'full details'. It also enumerates the returned fields, making the tool's scope unambiguous.

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?

It provides a targeted usage note for quests ('read objectives and rewards there, not from blocks'), but does not say when to use this tool versus alternatives like list_mnemons or search_mnemons. The implied usage (when you need full details of one entry) is clear but not explicitly contrasted.

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.