Skip to main content
Glama

YouSpot

by com.youspot
OverviewDiscussionsAdmin

Merge brain objects

merge_graph_objects

Merge two duplicate records in the user's graph into one, person or company only. Every connection moves from the duplicate onto the kept record, fields the kept record lacks are copied over (never overwritten), and the duplicate is removed. Call with preview=true first and emit the merge_compare card it names: the card shows both records and merges when the user clicks, so never merge without an explicit yes. keep_id survives; merge_id goes. unmerge_graph_objects puts it back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keep_idYesThe record that survives (exact object_id).
previewNoReturn what the merge would do without doing it. Call this first.
merge_idYesThe duplicate to fold in and delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / preview
      Added value: +{
+  "description": "Return what the merge would do without doing it. Call this first.",
+  "type": "boolean"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give readOnlyHint=false; the description adds that connections move, fields are copied without overwriting, the duplicate is removed, and the kept record survives. It also discloses the need for user confirmation, which is beyond the annotation.

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?

The description is four short, dense sentences. It front-loads the core purpose, then the workflow, then specifics. No filler or redundant phrasing.

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?

Given the destructive nature, the description covers the operation, prerequisites (preview), data behavior, and reversibility. It could mention error conditions, but it is sufficiently complete for an agent to call correctly.

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%, but the description adds meaning: 'keep_id survives; merge_id goes' clarifies roles, and 'Call with preview=true first' adds usage semantics for the preview parameter. It enriches the schema's parameter descriptions.

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?

The description states a specific verb 'merge' and resource 'two duplicate records in the user's graph', and adds scope 'person or company only'. It distinguishes from siblings like connect_graph_objects (connecting distinct objects) and delete_graph_objects (deleting one) by detailing the merge behavior.

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?

The description gives an explicit workflow: call with preview=true first and never merge without an explicit yes. It also mentions the reversal via unmerge_graph_objects. However, it does not explicitly name alternative tools for the same scenario, though the guidance is strong.

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

All YouSpot toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources