Skip to main content
Glama
itseasy21

Knowledge Graph Memory Server

create_relations

Adds multiple new connections between entities in a knowledge graph to establish relationships using active voice descriptions.

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

  • index.ts:93-107 (handler)
    The core handler function in KnowledgeGraphManager that implements the logic for creating new relations: loads the graph, filters out duplicates based on from/to/relationType, adds timestamps and versions, appends to graph, saves, and returns the new 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
      )).map(r => ({
        ...r,
        createdAt: new Date().toISOString(),
        version: r.version || 1
      }));
      graph.relations.push(...newRelations);
      await this.saveGraph(graph);
      return newRelations;
    }
  • The JSON schema defining the input structure for the 'create_relations' tool, specifying an array of relations each with 'from', 'to', and 'relationType'.
    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:310-331 (registration)
    Registration of the 'create_relations' tool in the list of tools returned by ListToolsRequestSchema handler.
    {
      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:516-517 (registration)
    Dispatch case in the CallToolRequestSchema handler that invokes the createRelations method with parsed arguments and formats the response.
    case "create_relations":
      return { content: [{ type: "text", text: JSON.stringify(await knowledgeGraphManager.createRelations(args.relations as Relation[]), null, 2) }] };
  • TypeScript interface defining the structure of a Relation object used by the createRelations handler.
    interface Relation {
      from: string;
      to: string;
      relationType: string;
      createdAt: string;
      version: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation (implying mutation) but doesn't address permissions, side effects, error handling, or response format. The 'active voice' note is trivial and doesn't add meaningful behavioral context for an AI agent.

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 front-loaded with the core purpose. The second sentence about 'active voice' is arguably unnecessary for tool selection but doesn't significantly detract from conciseness. Overall efficient with minimal waste.

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?

For a mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what 'create' entails operationally, how relations are validated, what happens on conflicts, or what the tool returns. Given the complexity and lack of structured support, more contextual information is needed.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'relations between entities' which aligns with the 'relations' parameter, but doesn't explain the structure, constraints, or semantics beyond what's implied. The description adds minimal value over the bare schema, meeting baseline expectations but not compensating fully for the coverage gap.

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 resource ('between entities in the knowledge graph'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'update_relations' or 'delete_relations', which would require more precise scope definition.

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 no guidance on when to use this tool versus alternatives like 'update_relations' or 'create_entities'. The mention of 'active voice' is a stylistic requirement rather than functional usage guidance. No prerequisites, exclusions, or comparative context with sibling tools are provided.

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/itseasy21/mcp-knowledge-graph'

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