llm-migrate

Overview Schema Source Related Servers Discussions Admin

Submit Adapted File

submit_adapted_file

Submit a complete post-adaptation application file for review, or mark it unchanged to use the original without resending.

Instructions

Store one finalized post-adaptation application file for review.

adapted_content must be the complete file, not a diff. Submissions are checked deterministically (path containment, Python syntax, model-id consistency) and written beneath <run>/output/files/; the application tree itself is never modified. If the file genuinely needs no change for the target model, pass unchanged=true with an empty adapted_content: the original is copied as the deliverable and the coverage gap closes without resending the file. Prompt source files are rejected here; submit them with submit_adapted_prompt instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`changes`	Yes
`run_dir`	Yes
`new_file`	No
`rationale`	Yes
`unchanged`	No
`source_path`	Yes
`adapted_content`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.0Sep 19, 2026
- addedInput schema / properties / unchanged
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
Addedv1.2.0Sep 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full transparency burden. It discloses deterministic checks, the output destination, that the application tree is never modified, and that prompt files are rejected. This is strong behavioral disclosure for a submission/mutation tool.

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?

The description is dense but every sentence earns its place: purpose, format constraint, validation behavior, no-modification guarantee, and the unchanged alternative. It is front-loaded with the main purpose and then adds critical operational details without fluff.

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 description covers the core behavior, constraints, destination, and sibling routing, which makes the tool usable. It loses one point because several parameters still lack semantic explanation, and with no annotations the overall definition is not fully self-contained for a correct invocation.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It explains adapted_content and unchanged well, but leaves run_dir, source_path, rationale, changes, and new_file without any added meaning beyond their names and types. An agent has to guess the exact expected semantics for five of seven parameters.

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 opening sentence states a specific verb ('Store') and resource ('one finalized post-adaptation application file') with clear scope. It also explicitly distinguishes itself from submit_adapted_prompt by saying prompt source files are rejected here and should go there.

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

Usage Guidelines5/5

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

The description tells the agent when to submit normally, when to use unchanged=true, what format is required, and explicitly rejects prompt files while naming the correct sibling tool. This gives clear when/when-not guidance with alternatives.

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