Skip to main content
Glama
Sign In
Context+

Context+

by forloopcodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_relation

Establish typed connections between memory nodes to build semantic relationships within codebases, supporting various relation types with weighted edges that update automatically.

Instructions

Create a typed edge between two memory nodes. Supports relation types: relates_to, depends_on, implements, references, similar_to, contains. Edges have weights (0-1) that decay over time via e^(-λt). Duplicate edges update weight instead of creating new ones.

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": {
      "source_id": "<source_id>",
      "target_id": "<target_id>",
      "relation": "<relation>"
    },
    "name": "create_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesID of the source memory node.
target_idYesID of the target memory node.
relationYesRelationship type between nodes.
weightNoEdge weight 0-1. Higher = stronger relationship. Default: 1.0.
metadataNoOptional key-value metadata for the edge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

A4.4/5.0
Behavior5/5

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

Superior disclosure despite no annotations. Uniquely documents temporal decay physics (e^(-λt)) and idempotent upsert behavior on duplicates—critical behavioral traits for a write operation that agents need to understand for correct invocation and expectation-setting.

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?

Four precisely ordered sentences spanning purpose, valid types, physics, and uniqueness constraints. Zero waste—every clause earns its place. Front-loaded with the core action, followed by necessary constraints and behaviors.

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?

Comprehensive for a graph mutation tool without output schema. Covers unique domain logic (decay, duplicates) that schema cannot express. Minor gap: does not explicitly state prerequisite that source/target nodes must exist (implied but not guaranteed).

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?

With 100% schema coverage, baseline is 3. Description adds value by contextualizing the weight parameter (decay mechanics, 0-1 range emphasis) and implying directional semantics via 'typed edge'. Lists enum values explicitly, slightly redundant with schema but reinforces valid options.

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?

Excellent specificity with clear verb 'Create' and resource 'typed edge between two memory nodes'. Distinctly differentiates from sibling node-creation tools (upsert_memory_node) and retrieval tools by explicitly mentioning edges/relationships.

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?

Provides implicit guidance through enumeration of relation types and duplicate-handling behavior, but lacks explicit 'when to use this vs alternatives' guidance. Does not clarify when to prefer this over add_interlinked_context or prerequisite that nodes must exist first.

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