Skip to main content
Glama

update_edges

DestructiveIdempotent

Modify existing knowledge graph edges by changing source or target nodes, edge type, or weight. Use it to correct relationships and keep graph data accurate.

Instructions

Update existing edges 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": {
      "edges": "<edges>"
    },
    "name": "update_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYesArray of edges to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the update replaces the whole edge or patches fields, how renaming via newFrom/newTo affects node references, or what happens when an edge is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero redundancy and the verb front-loaded, but it is under-specified rather than genuinely concise. The brevity costs information the agent needs about a nested-array mutation.

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?

The tool takes an array of edge objects with both current and replacement fields, which is non-trivial, yet the description never explains the rename/patch semantics or error behavior. With no output schema present, the description should do more to describe what a successful update returns or how partial failures are handled.

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%, so the nested fields (from/to/edgeType as current values, newFrom/newTo/newEdgeType/newWeight as replacements) are already documented in the schema. Baseline 3 applies since the description adds no extra semantics about the current-vs-new pairing or weight defaults.

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: 'Update existing edges in the knowledge graph'. An agent can tell this mutates existing edges rather than creating them. It does not, however, distinguish itself from siblings like add_edges, delete_edges, or update_nodes, so the differentiation is left to the name alone.

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 guidance on when to use this tool versus add_edges or delete_edges, and no prerequisites such as whether the referenced edge must already exist. The only implied usage is 'edges exist and need modification', which the agent must infer.

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