compare_constructions
Align two constructs' build procedures step by step, in order — was this built the same way as that?
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": {
"against": "<against>"
},
"name": "compare_constructions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | what to align on: `abstract` is the PROCEDURE (the command with its molecules abstracted away, so the same method on different DNA still matches); `processId` is the EXACT recorded operation, identical only when the very same step ran on the very same molecules. | abstract |
| _files | No | The project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name. | |
| against | Yes | File id or name of the construct to compare against, in the same project. | |
| _subject | No | The record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several. | |
| document | No | File id or name for THIS side. The focused document when omitted. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rows | Yes | the whole aligned history, row by row: shared, only-here, or only-there | |
| shared | Yes | steps both procedures have, in the same order | |
| similarity | Yes | shared steps as a percentage of the alignment |