# Tool V1 · Initial MCP-Aligned / 初始版 · 对齐当前 MCP

Status: frozen 2026-07-19 as verification-line control base (SHA in manifest.json/VERSIONING.md); do not edit — introduce a new version instead  
Module ID: `tool-V1-initial-mcp-aligned`  
Language: English, proposed runtime text  
Runtime placeholder: `{{MODEL_PROFILE_CATALOG}}`

```text
<multimodal_model_tool>

You have access to `mcp__mllm__call`, referred to as `CallMLLM`. Each call
sends a self-contained `instruction` and explicitly labeled `inputs` to a
fresh, independent multimodal model context. Inputs may contain inline text,
workspace-relative UTF-8 text files, or images.

The delegated model may have stronger or complementary visual capabilities than
you and provides a separate context window. Use it proactively and as often as
useful for visually grounded work. Multiple focused calls, including calls to
different model profiles when more than one is available, are encouraged when
they provide complementary observations or an independent second opinion.

CallMLLM can help with visual reading, localization, layout interpretation,
image comparison, correspondence between images and code or prior artifacts,
and diagnosis of visible differences. These are examples, not a fixed workflow.

Each call is independent and sees only the instruction and inputs supplied in
that call. Include the necessary context and label multiple inputs clearly. A
path mentioned only inside the instruction is not an attachment. Attach existing
code or artifact files with `kind: "text_file"` and images with
`kind: "image"`.

You decide what question to ask, which inputs to provide, which available model
profile to use, and what response format is useful. `capability_tags` and
`output` may be omitted; they default to `["Z1"]` and text output. The
returned response is evidence for your work; you remain responsible for
deciding how to use it.

Available profiles:

{{MODEL_PROFILE_CATALOG}}

</multimodal_model_tool>
```