Skip to main content
Glama

split_condition

Detach a twin condition from its family so material rows freeze at current values and edits to the original stop reaching it. Use when variants have diverged.

Instructions

Cut a twin loose from its family: every following material row freezes at its current values and edits to the original stop reaching it. It keeps its finish tag and still groups with its siblings — only the inheritance ends. Use when two variants have diverged far enough that following one another is wrong. A condition that already owns its materials returns split:false rather than erroring. Reversible with undo_last.

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": {
      "condition": "<condition>"
    },
    "name": "split_condition"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionYesFinish tag of the twin to split, e.g. 'CPT-1 – Level 2'

Output Schema

NameRequiredDescriptionDefault
noteYes
splitYesfalse = it already owned its materials; nothing was following
conditionYes
family_idNoKept — it still groups with its siblings
frozen_rowsYesFollowing rows frozen at their current values
condition_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.31
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / frozen_rows / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / frozen_rows / minimum
      Added value: +-9007199254740991
  2. Addedv0.1.14

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the freeze-on-current-values semantics, that the finish tag is retained, that sibling grouping survives, that already-owning conditions return split:false instead of erroring, and that undo_last reverses it. Gaps remain around permissions or side effects on other users, but the mutation profile is genuinely well described.

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 behavioral facts are front-loaded before the usage guidance, and the edge-case and reversibility notes are short. The 'twin/family/siblings' metaphor is repeated across several clauses and could be tightened, but nothing is padded.

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 mutation with an output schema present, the description covers what changes, what persists, the no-op case, and how to undo. Only permission or scope caveats are absent, which is a minor omission given the tool's simplicity.

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 coverage is 100% and the single parameter is documented as a finish tag with an example, so the schema already does the work. The description adds only indirect color ('its finish tag') and no format or matching nuance beyond the schema, so 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 uses a concrete verb-and-object framing ('Cut a twin loose from its family') and explains precisely what is severed: material rows freeze at current values and edits to the original stop propagating. It never names a sibling such as duplicate_condition or edit_condition to sharpen the boundary, so it falls short of a 5.

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 an explicit trigger — 'Use when two variants have diverged far enough that following one another is wrong' — which is a real decision rule an agent can apply. It stops short of stating when-not-to-use or naming the alternative tool to pick instead, so it is clear context without full routing.

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