Skip to main content
Glama

add_nodes

Add multiple new nodes to a knowledge graph in one call, letting you build or extend structured memory with names, types, and metadata.

Instructions

Add multiple new nodes in the knowledge graph

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": {
      "nodes": "<nodes>"
    },
    "name": "add_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesArray of nodes to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds only the word "new", which vaguely implies duplicate names may be rejected, but it does not say whether the call is atomic across the array, what happens on name collision, or what identifiers come back for the created nodes.

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?

A single front-loaded sentence naming the verb, resource, quantity, and domain, with no filler. It is efficient, though its brevity comes at the cost of the behavioral detail an agent would want before calling it.

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 batch-create tool with annotations and a fully documented schema, the essentials are present, so it is minimally viable. The gaps are duplicate-name behavior and any indication of what the call returns, neither of which the absent output schema compensates for.

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 100%: every parameter, including the nested name, nodeType, and metadata fields, is documented in the schema itself. The description contributes nothing further about the array shape or per-node requirements, so the baseline 3 applies.

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 states a specific verb ("Add") and resource ("nodes") plus the domain ("knowledge graph"), and "multiple" signals batch creation, which separates it from add_edges/add_npc. It does not explicitly distinguish itself from update_nodes or explain how a "new" node differs from an updated one, so it stops short of full sibling differentiation.

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?

There is no stated context for when to use this over update_nodes or add_metadata, and no exclusions. The only implicit guidance is the word "multiple", which hints at batch use, but nothing tells the agent when a single-node or update path is more appropriate.

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