Skip to main content
Glama

consolidate_graph

Identify graph entities that refer to the same thing, preview suggested merges, then apply them to fold each group into one canonical entity.

Instructions

Ask a model which graph entities are the same thing under different names. The default is a preview that returns the suggested merges. Review them, then call with apply=true to fold each group into one canonical entity.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consolidate_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the crucial safety trait: the default is non-destructive preview and mutation only happens with apply=true. It also reveals that a model is invoked, implying non-deterministic, possibly costly output. It does not say whether a merge is reversible, what happens to aliases/edges of the folded entities, or whether a model provider must be configured.

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?

Three short sentences ordered as purpose, default behavior, and commit path. The preview/apply distinction is front-loaded and nothing is redundant.

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?

For a one-parameter tool with no output schema, the description covers intent, the safe default, the commit action, and roughly what the preview returns. Remaining gaps are the shape of the returned merge groups and the scope of the graph scanned, which are minor but real for a mutation tool.

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 0%, so the description must explain the single parameter, and it does: apply=true is the commit switch versus the default preview. It does not discuss the default value explicitly beyond 'the default is a preview,' but the semantics of the only parameter are fully conveyed.

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 names a specific operation (use a model to detect graph entities that are aliases of one another and consolidate them) rather than restating the tool name. It is distinct from read-only siblings like find_entity or get_backlinks, though it never explicitly says so.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear two-step workflow: call with defaults to preview suggested merges, review them, then re-call with apply=true to commit. It does not address when to prefer this over manual curation via upsert_concept or how to scope which entities get considered, so exclusions are absent.

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