Skip to main content
Glama
Sign In
ecu-harness

ecu-harness

by omaratif1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Finish the change

ecu_change_finish

Validate and close an open ECU configuration change by writing a review report for the human reviewer. Records the summary of what changed and why; nothing is committed to version control.

Instructions

Validate and close the open change. Writes the review report for the user. Nothing is committed to version control.

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": {
      "summary": "<summary>"
    },
    "name": "ecu_change_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYesWhat was changed and why, for the human reviewer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses two useful behavioral facts: it writes a review report for the human, and nothing is committed to version control. What it does not cover is what happens to the change afterwards and whether re-invocation is safe, which matters given idempotentHint=false.

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?

Three short sentences, action first, scope constraint last, with no filler. Every sentence contributes a distinct fact an agent needs.

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, no-output-schema tool this is nearly complete: the write behavior and the version-control guarantee are both stated. The remaining gap is that it does not indicate what the call returns or what state the change ends in, which the absence of an output schema makes worth spelling out.

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?

There is a single parameter and schema description coverage is 100%, with the schema itself explaining the summary is 'What was changed and why, for the human reviewer.' The description adds no further parameter meaning, 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 gives a specific verb pair and resource: 'Validate and close the open change', plus the side effect of writing a review report. It is clearly a terminal step distinct from ecu_change_diff or ecu_change_discard in intent, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling it the step that 'closes' the open change implies it is the final action after editing/validation, but there is no explicit when-to-use statement, no condition distinguishing it from ecu_change_discard, and no stated preconditions (e.g. that a change must already be open).

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