Skip to main content
Glama
yodakeisuke

Knowledge Graph Memory Server

by yodakeisuke

create_relations

Adds multiple connections between entities in a knowledge graph using active voice relations to build persistent memory for chat applications.

Instructions

Create multiple new relations between entities in the knowledge graph. Relations should be in active voice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relationsYes

Implementation Reference

  • Core handler function for creating relations. Loads the knowledge graph, filters out duplicate relations, appends new ones, saves to persistent storage, and returns the newly created relations.
    async createRelations(relations: Relation[]): Promise<Relation[]> {
      const graph = await this.loadGraph();
      const newRelations = relations.filter(r => !graph.relations.some(existingRelation => 
        existingRelation.from === r.from && 
        existingRelation.to === r.to && 
        existingRelation.relationType === r.relationType
      ));
      graph.relations.push(...newRelations);
      await this.saveGraph(graph);
      return newRelations;
    }
  • Type definition for Relation used in the create_relations tool input.
    interface Relation {
      from: string;
      to: string;
      relationType: string;
    }
  • index.ts:390-411 (registration)
    Tool registration in ListToolsRequestHandler, including name, description, and input schema for create_relations.
    {
      name: "create_relations",
      description: "Create multiple new relations between entities in the knowledge graph. Relations should be in active voice",
      inputSchema: {
        type: "object",
        properties: {
          relations: {
            type: "array",
            items: {
              type: "object",
              properties: {
                from: { type: "string", description: "The name of the entity where the relation starts" },
                to: { type: "string", description: "The name of the entity where the relation ends" },
                relationType: { type: "string", description: "The type of the relation" },
              },
              required: ["from", "to", "relationType"],
            },
          },
        },
        required: ["relations"],
      },
    },
  • index.ts:555-556 (registration)
    Dispatch handler in CallToolRequestHandler switch statement that invokes the createRelations function.
    case "create_relations":
      return createResponse(JSON.stringify(await knowledgeGraphManager.createRelations(args.relations as Relation[]), null, 2));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation ('Create multiple new relations'), implying mutation, but fails to address critical aspects like permissions needed, whether changes are reversible, error handling, or rate limits. The active voice note is trivial and doesn't compensate for the lack of substantive behavioral information.

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 brief and to the point with two sentences, avoiding unnecessary verbosity. However, the second sentence ('Relations should be in active voice') feels somewhat misplaced and doesn't contribute significantly to tool understanding, slightly reducing efficiency.

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?

Given the complexity of a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is insufficient. It doesn't explain return values, error conditions, or provide enough context to use the tool effectively, leaving significant gaps in understanding for the agent.

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?

The schema description coverage is 0%, so the description must compensate, but it only vaguely references 'relations' without explaining the structure or semantics of the 'relations' array parameter. It adds minimal value beyond the schema, which already defines the properties ('from', 'to', 'relationType'), resulting in a baseline score due to inadequate parameter clarification.

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 multiple new relations') and the resource ('between entities in the knowledge graph'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'create_entities' or 'delete_relations', which would require more specific context about when to use each.

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

Usage Guidelines2/5

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

The description provides minimal guidance with the phrase 'Relations should be in active voice', which is a stylistic hint rather than usage advice. It lacks explicit when-to-use instructions, prerequisites, or alternatives compared to siblings like 'create_entities' or 'delete_relations', leaving the agent without clear contextual direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yodakeisuke/mcp-memory-domain-knowledge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server