Skip to main content
Glama

duplicate_condition

Creates a linked twin of an existing condition with a required label, inheriting and following its materials list while allowing row-level overrides for the new area.

Instructions

Twin a condition — the same finish measured somewhere else, with its own supporting materials. One finish in two areas is not two conditions and it is not one either: the same sheet goods over a slab and over a raised deck take the same field material and different preparation underneath (one wants a moisture barrier, the other a primer and a different adhesive). The twin arrives carrying the original's whole materials list and keeps FOLLOWING it — change a coverage rate on the original and every twin that has not touched that row gets it; edit a row on the twin and only THAT row stops following. label is REQUIRED and becomes the tag suffix ('CPT-1' + 'Level 2' → 'CPT-1 – Level 2'), because every tool in this server resolves a condition by finish tag and takes the FIRST match: two conditions sharing a tag would make one permanently unreachable, and a takeoff re-import collapses them last-wins. A label already in use is refused rather than de-collided. No takeoffs come along — measure the new area against the returned condition_id. Reversible with undo_last; use split_condition to end the inheritance permanently.

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>",
      "label": "<label>"
    },
    "name": "duplicate_condition"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesWhat makes this one different, usually the area: 'Level 2', 'Building B', 'Phase 2'
conditionYesFinish tag of the condition to twin, e.g. 'CPT-1'

Output Schema

NameRequiredDescriptionDefault
noteYes
conditionYesThe twin's finish tag — base tag + the label, e.g. 'CPT-1 – Level 2'
family_idYesShared by every variant of this finish — survives a split
variant_ofYesThe condition whose material rows this one follows
condition_idYesThe TWIN — measure the new area against this
variant_labelYes
inherited_rowsYesMaterial rows copied, all still following the original

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior5/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 so: live inheritance of the materials list, per-row detachment on edit, first-match tag resolution, last-wins collapse on re-import, duplicate-label refusal instead of de-collision, and reversibility via undo_last. These are non-obvious behaviors an agent could not infer from the schema.

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?

Purpose is front-loaded, but the middle is discursive - the slab-versus-deck moisture barrier/primer illustration is evocative yet costs several sentences for a single point about shared finish versus differing prep. Dense parenthetical and backtick-heavy phrasing makes it slower to scan than necessary.

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?

The critical behaviors for a duplication tool with inheritance semantics are covered: what carries over, what does not (no takeoffs), how to undo, and how to make the split permanent. An output schema exists so return-value detail is rightly omitted; minor gaps are authorization or scope-level constraints, which are not addressed.

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%, so the baseline is 3; the description adds real meaning by explaining how label is consumed ('CPT-1' + 'Level 2' → 'CPT-1 – Level 2') and that condition is resolved as a finish tag where the first match wins. The collision-refusal rule for label is similarly not derivable from the schema.

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?

Opens with a specific verb and resource ('Twin a condition') and immediately scopes what a twin is: the same finish measured elsewhere with its own supporting materials. It explicitly separates itself from the related sibling by naming split_condition and the differing outcome (permanent inheritance break vs. live following).

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?

States that the new area should be measured against the returned condition_id and that split_condition is the alternative when inheritance should end permanently. It does not explicitly state when NOT to duplicate versus create a fresh condition, but the guidance present is concrete.

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