v8unpack-mcp

Overview Schema Source Related Servers Discussions Admin

diff

Compare two unpacked 1C directories object by object. Detects content differences in code, JSON, XML forms, and marks binary file changes, with option to show only change facts.

Instructions

Сравнить два распакованных каталога (результат unpack) пообъектно. По содержимому (построчный diff): .mxl (декодируется структурно), .json, .obj.bsl, XML форм. По байтам (только факт изменения, помечается binary=true): зашифрованные .obj.bin, СКД .bin, картинки. full=false — только факт изменения без диффа

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": {
      "dir_a": "<dir_a>",
      "dir_b": "<dir_b>"
    },
    "name": "diff"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No
`dir_a`	Yes
`dir_b`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it explains content-based line-by-line diffing for structured formats, byte-level change detection for binary formats, and the meaning of full=false. It also discloses the binary=true marker behavior without any contradiction.

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?

Two dense sentences cover scope, file-type routing, comparison modes, and flag semantics with zero filler. The main purpose is front-loaded, followed by structured technical details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no annotations, the description provides enough behavioral detail for an agent to invoke diff correctly: input requirements, file-category behavior, and the effect of the only optional parameter. The presence of an output schema covers return-value expectations.

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

Parameters4/5

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

Schema coverage is 0%, so the description compensates by explaining the full parameter's behavior explicitly. It identifies dir_a and dir_b as the two unpacked directories, though it does not clarify comparison direction/order semantics, which is a minor gap.

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 precise verb and resource: compare two unpacked directories object-by-object. It enumerates the file types and comparison modes, so the tool's role is unmistakable and clearly distinguished from sibling tools like unpack/repack.

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?

The description makes clear this tool operates on two unpacked directories (the result of unpack), giving strong context for when to call it. It does not explicitly name alternatives or exclusions, but the usage context is unambiguous enough for agent selection.

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