Skip to main content
Glama

ECO Create

eco_create
Destructive

Create an Engineering Change Order record with affected items, disposition, and effectivity, and optionally embed lockfile-based where-used impact so the change's blast radius travels with it.

Instructions

Build an ECO change-order record (issue #142, C3) — turn a change into a record, not a silent mutation (the diff IS the change order, mapping onto a git commit/PR). Optionally compute its where-used impact over a lockfile in the same call, so the blast radius travels with the record.

id: the ECO id (e.g. "ECO-0001"). affected: the list of changed item / component ids. disposition: the change disposition (use_as_is | rework | scrap | revise | ...). effectivity: a dict with exactly one of date|serial|revision (when it takes effect). title / note: optional human description recorded on the record. interface_change: true if a published interface moved (the §9 stale trigger). lockfile: optional path — when given, the result embeds an impact report. out: optional path — write the git-diffable ECO sidecar there.

Returns the ECO object (with impact when a lockfile is supplied); a malformed ECO fails loudly.

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": {
      "id": "<id>",
      "affected": "<affected>",
      "disposition": "<disposition>",
      "effectivity": "<effectivity>"
    },
    "name": "eco_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
outNo
noteNo
titleNo
affectedYes
lockfileNo
workspaceNoRun this call in this named workspace
dispositionYes
effectivityYes
interface_changeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as non-readonly and destructive. The description adds useful beyond-annotation behavior: malformed ECOs fail loudly, a supplied lockfile embeds an impact report, and out writes a git-diffable sidecar. It does not disclose overwrite semantics or permission requirements, keeping it below 5.

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 purpose is front-loaded and the parameter notes are organized and mostly necessary. Some references such as issue #142, C3, and the §9 stale trigger are less useful to an agent, but they do not seriously harm 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?

For a 10-parameter mutation with a nested effectivity object and no output schema, the description explains the return shape, optional impact embedding, sidecar output, and failure mode. It could say more about persistence, uniqueness of id, or overwrite behavior for out, but it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10%, so the description carries most parameter meaning. It documents id, affected, disposition values, effectivity's exactly-one-of date/serial/revision constraint, optional title/note, interface_change, lockfile, and out; workspace is already described in 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?

The description states a specific verb and resource: 'Build an ECO change-order record.' It also distinguishes the operation conceptually from a silent mutation by explaining that the diff is the change order and maps to a git commit/PR, so an agent can understand its role even without sibling names.

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 clear usage context, including that lockfile optionally computes where-used impact in the same call and that out writes a sidecar. It does not explicitly name alternatives such as eco_validate or change_impact or state when not to use this tool, so it falls short of full alternative guidance.

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

Deploy Server

Other Tools