Skip to main content
Glama

split_entity

Repair over-merged entities by moving a predicate-selected subset of observations to a new or existing entity, without modifying observation content.

Instructions

R5 inverse of merge_entities. Re-points a predicate-selected subset of an entity's observations onto a new or pre-existing entity to repair over-merges (typically the pre-v1.2 heuristic name_key:title collapse on session-scoped types). Schema-agnostic predicate — supply any of observed_at_gte, source_id_in, or observation_field_equals. Observation content is never modified; only entity_id FK is re-bound. Idempotent via (user_id, idempotency_key) — reuse with a different predicate returns ERR_IDEMPOTENCY_MISMATCH. Typed relationships remain bound to the source; rebuild them with create_relationship.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_entity_idYes
predicateYesR5: declarative predicate describing which observations of the source entity should be re-pointed onto the new entity. Every form reads a column every observation row carries so the predicate surface is schema-agnostic. At least one form MUST be supplied.
new_entityYes
idempotency_keyYesRequired per MUST #11. Reuse with a different predicate returns `ERR_IDEMPOTENCY_MISMATCH`; reuse with the same predicate returns the original split result (`replayed: true`).
reasonNoFree-text rationale recorded on the audit row.
user_idNo
Behavior4/5

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

Given no annotations, the description discloses key behaviors: observation content unmodified, idempotency mechanism, and relationship binding. It omits side effects like audit logging, but covers essential traits.

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?

The description is a single dense paragraph; it conveys necessary information concisely but could be better structured (e.g., bullet points) for readability.

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?

Covers core functionality, predicate usage, idempotency, and relationship handling. Missing error responses beyond the mismatch error, but adequate for a complex tool with no output schema.

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?

The description adds value beyond the 50% schema coverage by explaining the predicate's schema-agnostic nature and available forms, and the role of idempotency_key. Some schema fields (e.g., source_entity_id) lack additional context, but overall compensation is strong.

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 clearly states it is the inverse of merge_entities, using specific verbs and resources ('re-points observations onto a new or pre-existing entity to repair over-merges'). It distinguishes from sibling tools and provides context about typical use.

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 explains schema-agnostic predicate selection and idempotency behavior, but lacks explicit when-not-to-use guidance or alternatives beyond mentioning create_relationship for rebuilding typed relationships.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markmhendrickson/neotoma'

If you have feedback or need assistance with the MCP directory API, please join our Discord server