Skip to main content
Glama

add_edges

Add multiple directed edges between knowledge graph nodes to define relationships, with optional weights and active-voice edge types for accurate graph modeling.

Instructions

Add multiple new edges between nodes in the knowledge graph. Edges should be in active voice

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": {
      "edges": "<edges>"
    },
    "name": "add_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYesArray of edges to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the mutation profile is known. The description adds that edges are added in bulk and are 'new,' but says nothing about what happens when referenced nodes don't exist, whether duplicate edges are created, or whether the operation is atomic across the array.

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?

Two short sentences, front-loaded with the action and scope; no filler. The trailing active-voice rule is terse but useful and does not bloat the definition.

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

Completeness3/5

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

For a simple one-parameter bulk-insert tool with full schema coverage and annotations, the core is covered. It falls short on mutation edge cases an agent would want: node existence requirements, duplicate handling, and atomicity of partial failures.

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?

Schema coverage is 100%, so every nested field (from, to, edgeType, weight) is already documented. The description adds real meaning beyond the schema by prescribing active-voice phrasing for edgeType and emphasizing that the array accepts multiple edges at once.

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?

States a specific verb and resource: adding multiple new edges between nodes in the knowledge graph. The verb distinguishes it from delete_edges and update_edges, though it does not explicitly name those alternatives.

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?

No guidance on when to use this versus update_edges or add_nodes, and no prerequisites (e.g., whether nodes must already exist). The only guidance given is the 'active voice' convention for edges, which is a formatting rule rather than a when-to-use rule.

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