Create multiple knowledge graph entities with observations, confidence levels, temporal validity, and project scoping for persistent, structured memory storage.
Create multiple new entities in the knowledge graph. Supports v1.6 freshness (ttl/confidence), v1.8 project scoping, and η.4.4 bitemporal validity (validFrom/validUntil/observationMeta).
| Name | Required | Description | Default |
|---|---|---|---|
| entities | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v12.7.0Input schema / properties / entities / items / properties / confidenceAdded value: +{
+ "description": "v1.6 freshness — belief strength [0, 1]",
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+}Input schema / properties / entities / items / properties / importanceAdded value: +{
+ "description": "Optional importance score (0-10) for prioritization",
+ "maximum": 10,
+ "minimum": 0,
+ "type": "number"
+}Input schema / properties / entities / items / properties / observationMetaAdded value: +{
+ "description": "η.4.4 per-observation temporal metadata; indexed parallel to observations[] by content match",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "content": {
+ "description": "Matches an entry in observations[] by exact content",
+ "type": "string"
+ },
+ "recordedAt": {
+ "description": "Bitemporal axis — when the fact was recorded",
+ "type": "string"
+ },
+ "validFrom": {
+ "type": "string"
+ },
+ "validUntil": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "content"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Input schema / properties / entities / items / properties / parentIdAdded value: +{
+ "description": "Optional parent entity name for hierarchical nesting",
+ "type": "string"
+}Input schema / properties / entities / items / properties / projectIdAdded value: +{
+ "description": "v1.8 project scope identifier",
+ "type": "string"
+}Input schema / properties / entities / items / properties / tagsAdded value: +{
+ "description": "Optional lowercase tags for categorization",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / entities / items / properties / ttlAdded value: +{
+ "description": "v1.6 freshness — seconds until entity is considered stale",
+ "type": "number"
+}Input schema / properties / entities / items / properties / validFromAdded value: +{
+ "description": "η.4.4 ISO 8601 — entity is valid from this instant. Absent ⇒ always valid since creation.",
+ "type": "string"
+}Input schema / properties / entities / items / properties / validUntilAdded value: +{
+ "description": "η.4.4 ISO 8601 — entity is valid until this instant. Absent ⇒ still valid.",
+ "type": "string"
+}v11.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions supported features but does not disclose side effects, idempotency, error behavior, or permissions. Behavioral context is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose and key version features. No redundancy, but could be slightly more concise by omitting version labels.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the large sibling list and no output schema, the description does not differentiate from similar creation tools or explain what happens on success/failure. Lacks guidance on when to use this vs add_observations or create_relations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
While the input schema has full descriptions for most parameters, the description adds contextual grouping by version features (v1.6, v1.8, η.4.4). However, with schema description coverage at 0% (description does not re-state params), it adds moderate value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it creates multiple new entities in a knowledge graph, using specific verbs and resource. It distinguishes itself from siblings that are more specific (e.g., create_relations, add_observations).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like create_relations or add_observations. The description does not mention prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielsimonjr/memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server