server-memory

Overview Schema Source Related Servers Discussions Admin

create_relations

Create relations between existing entities by specifying source, target, and relation type. Optionally add weight and tags for richer connections.

Instructions

Create relations between entities.

Each relation needs: from (str), to (str), relationType (str). Optional: weight (float), tags (list[str]). Both entities must exist. Use active voice for relationType.

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": {
      "relations": "<relations>"
    },
    "name": "create_relations"
  }
}

Input Schema

Name	Required	Description	Default
`relations`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description adds moderate value by detailing required fields and constraints, but lacks details on side effects, failure modes, or idempotency.

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 concise (3 sentences), front-loaded with the purpose, and every sentence adds distinct value: action, field details, constraints.

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

Completeness4/5

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

Given an output schema exists, the description covers purpose, parameter structure, and key constraints. It omits behavioral details like idempotency, but is largely complete for a simple creation tool.

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?

Schema coverage is 0% and the schema uses additionalProperties: true, making it vague. The description fully compensates by listing all required and optional fields with types, providing essential meaning.

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 tool creates relations between entities, using the verb 'create' and resource 'relations'. It distinguishes from sibling tools like create_entities and delete_relations.

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 specifies a prerequisite ('Both entities must exist') and a style guideline ('Use active voice for relationType'), but does not provide explicit when-to-use or alternatives.

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