Skip to main content
Glama
Sign In
Novel Memory MCP

Novel Memory MCP

by syydmtl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_memories

Reads up to two specified full story stages for long-form roleplay history, so AI clients can retrieve only the exact past plot segments needed when the current scene spans multiple stages.

Instructions

一次读取最多两个指定的完整历史剧情阶段。

仅在当前剧情确实跨越多个阶段时使用；不会自动读取全部记忆。

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": {
      "memory_ids": "<memory_ids>"
    },
    "name": "get_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it usefully discloses the two-id ceiling and that retrieval is not automatic. It is silent on what happens if more than two ids are passed (error, truncation, or rejection) and on whether this is a harmless read or has side effects.

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 short sentences with zero filler: the operation and its size limit come first, then the usage condition and the negative constraint. Nothing is repeated from the schema.

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

Completeness3/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 no explanation, and the main calling constraint is stated. Still missing for a no-annotation tool are over-limit behavior and the meaning of '阶段' versus a single memory, which leaves the agent guessing at edge cases.

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 coverage is 0% and memory_ids has no format explanation, but the description does add real meaning by tying the parameter to a hard cardinality limit of two. What a memory id looks like and how to obtain one from the sibling tools remains undocumented anywhere.

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?

Names a concrete verb and resource ('一次读取最多两个指定的完整历史剧情阶段'), so the agent knows it returns full historical stage records, not summaries or tags. The '最多两个' scope also implicitly separates it from the singular get_memory sibling, though it never names that alternative.

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

Usage Guidelines4/5

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

Gives an explicit trigger ('仅在当前剧情确实跨越多个阶段时使用') plus a clear exclusion ('不会自动读取全部记忆'), which prevents needless bulk fetching. It stops short of naming search_memory or get_memory as the fallback when the plot does not span stages.

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

Deploy Server

Other Tools