Skip to main content
Glama
Sign In
Memento

Memento

by iAchilles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_entities

Creates multiple entities in a knowledge graph, inserting each if not present, with optional initial observations.

Instructions

Create entities in the knowledge graph. Inserts each entity if not exists and optionally seeds it with observations.

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
entitiesYesArray of entities to create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It mentions creation, existence check, and optional observation seeding, but omits details on error handling, return values, or side effects (e.g., what happens if an entity already exists).

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 convey the core purpose and key behavior with no unnecessary words. Every part earns its place.

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?

Given the moderate complexity (array of objects) and absence of output schema, the description covers basic purpose and behavior but lacks details on return values, errors, and relations to sibling tools. It is adequate but not fully complete.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the 'observations' parameter ('optionally seeds it with observations'), which goes beyond the schema's default description. This clarifies how the parameter is used.

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?

The description clearly states the action ('Create entities') and the resource ('knowledge graph'), distinguishing it from sibling tools like 'create_relations' or 'delete_entities'. However, it does not explicitly differentiate from similar creation tools or clarify limitations.

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 description implies idempotent behavior ('if not exists') but provides no explicit guidance on when to use this tool versus alternatives like 'add_observations' or 'create_relations'. No when-not-to-use cues are given.

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