Skip to main content
Glama
Sign In
Mnemosyne MCP

Mnemosyne MCP

by zhadyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_entities

Add multiple new entities to your knowledge graph memory. Specify names, types, and observations to batch-create persistent entities in the Memento memory system.

Instructions

Create multiple new entities in your Memento MCP knowledge graph memory system

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": {
      "entities": "<entities>"
    },
    "name": "create_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
entitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing behavior such as idempotency, validation, limits, or side effects. For a mutation tool, this is insufficient; an agent cannot anticipate what happens on failure or whether existing entities are affected.

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 one sentence, concise and front-loaded. It avoids unnecessary words. However, it is so brief that it omits essential information, making it too minimal for a complex tool.

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

Completeness2/5

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

The tool has a nested entity array with many optional fields, but the description offers no guidance on the input structure or return behavior. There is no output schema, so the description carries full responsibility for explaining the tool's behavior, which it fails to do.

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

Parameters2/5

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

The description says nothing about the parameters; schema description coverage is 0%. While the schema itself contains detailed property descriptions, the tool description does not add any meaning beyond what is structured, failing to compensate for the low coverage.

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 the action (create), the resource (multiple new entities), and the context (Memento MCP knowledge graph). This distinguishes it from sibling tools like create_relations or add_observations which target different resources.

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 usage is implied: use this when you need to add new entities. However, it provides no explicit guidance on when to choose this over alternatives, nor any prerequisites or exclusions. For a create operation, the intent is straightforward, but the lack of any alternative comparison leaves room for ambiguity.

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