argo-mcp

List mnemons

list_mnemons

Read-onlyIdempotent

List mnemon (lore/memory) entries for an Argo campaign. Optional filters: title (case-insensitive substring on entry title only) and type (e.g. NPC, Location, Quest). To find entries by what they CONTAIN, use search_mnemons instead. Returns up to limit entries (default 100); when hasMore is true, call again with offset = the returned nextOffset to fetch the next page. Each entry includes both title and entryId (shown inline as [id: …] and in structuredContent.idMap). Use the entryId verbatim for any tool that takes one; refer to entries by title in prose to the user.

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>"
    },
    "name": "list_mnemons"
  }
}

Input Schema

Name	Required	Description
`type`	No	Mnemon type filter (NPC, Location, Quest, …).
`limit`	No	Maximum entries to return (default 100).
`title`	No	Case-insensitive substring filter on title.
`offset`	No	Entries to skip. Pass the nextOffset from the previous call to fetch the next page.
`campaignId`	Yes	ID of the campaign.

Output Schema

Name	Required	Description	Default
`idMap`	Yes
`entries`	Yes
`hasMore`	Yes
`nextOffset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 5, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum entries to return (default 100).",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Entries to skip. Pass the nextOffset from the previous call to fetch the next page.",
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / nextOffset
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "entries",
-  "idMap"
-]New value: +[
+  "entries",
+  "idMap",
+  "hasMore"
+]

First observedMay 14, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds substantial behavioral detail: case-insensitive substring filtering, pagination semantics with hasMore/nextOffset, response contents (title, entryId, idMap), and the instruction to use entryId verbatim. This goes beyond what annotations convey and clarifies the tool's operation 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?

The description is dense but every clause earns its place: purpose, filter semantics, alternative tool, pagination behavior, response shape, and entryId usage. It is a single coherent paragraph with no filler or repetition, making it highly informative yet concise.

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 five parameters, output schema, and sibling tools, the description covers all essential aspects: what it lists, how filters work, how pagination works, what the response contains, and how to use identifiers. It is fully self-contained and sufficient for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Even though schema coverage is 100%, the description enriches parameter meaning: it specifies that title is a case-insensitive substring on title only, gives examples for type, explains limit default and maximum behavior, and details offset/nextOffset pagination semantics. This adds genuine value beyond the raw schema.

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 'List mnemon (lore/memory) entries for an Argo campaign,' a specific verb plus resource that clearly identifies the tool's function. It also distinguishes itself from search_mnemons by explicitly stating that search_mnemons is for finding entries by content, while this tool lists entries with optional filters.

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?

The description gives explicit guidance: use this tool for listing mnemon entries with optional title/type filters, and explicitly directs users to search_mnemons for content-based lookup. It also explains pagination usage ('when hasMore is true, call again with offset = the returned nextOffset') and entryId handling, providing clear when-to-use and alternatives.

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.