carve-mcp

Official

by markup-carve

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Migrate to Carve

carve_migrate

Read-only

Migrate HTML, Markdown, Djot, or BBCode source to Carve format while providing version 2 fidelity diagnostics for accurate conversions.

Instructions

Migrate HTML, Markdown, Djot, or BBCode source to Carve with version 2 fidelity diagnostics.

Input Schema

TableJSON Schema

Name	Required	Description
`format`	Yes
`source`	Yes	Document source (maximum 1000000 UTF-8 bytes)
`markdownDialect`	No	Opt-in Markdown flavor constructs; valid only for Markdown input.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`value`	Yes
`report`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.1.5Sep 22, 2026

changedInput schema / properties / format / enum

Previous value: -[
-  "html",
-  "markdown",
-  "djot"
-]New value: +[
+  "html",
+  "markdown",
+  "djot",
+  "bbcode"
+]

addedOutput schema / properties / report / properties / adapter
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / report / properties / diagnostics / items / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / report / properties / diagnostics / items / properties

Added value: +{
+  "code": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "column": {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  "confidence": {
+    "enum": [
+      "exact",
+      "inferred",
+      "fallback"
+    ],
+    "type": "string"
+  },
+  "fidelity": {
+    "enum": [
+      "preserved",
+      "normalized",
+      "degraded",
+      "dropped"
+    ],
+    "type": "string"
+  },
+  "line": {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  "message": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "path": {
+    "type": "string"
+  },
+  "severity": {
+    "enum": [
+      "info",
+      "warning",
+      "error"
+    ],
+    "type": "string"
+  }
+}

addedOutput schema / properties / report / properties / diagnostics / items / required

Added value: +[
+  "code",
+  "message",
+  "severity",
+  "fidelity",
+  "confidence"
+]

addedOutput schema / properties / report / properties / diagnostics / items / type
```
Added value: +"object"
```
addedOutput schema / properties / report / properties / mode
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / report / properties / schemaVersion / const
```
Added value: +2
```
removedOutput schema / properties / report / properties / schemaVersion / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / report / properties / schemaVersion / minimum
```
Removed value: --9007199254740991
```
changedOutput schema / properties / report / properties / schemaVersion / type
```
Previous value: -"integer"New value: +"number"
```
addedOutput schema / properties / report / properties / sourceFormat / enum
```
Added value: +[
+  "html",
+  "markdown",
+  "djot",
+  "bbcode"
+]
```

Changed2 schema fields changedv0.1.2Sep 6, 2026

addedInput schema / properties / markdownDialect

Added value: +{
+  "additionalProperties": false,
+  "description": "Opt-in Markdown flavor constructs; valid only for Markdown input.",
+  "properties": {
+    "abbreviations": {
+      "type": "boolean"
+    },
+    "attributes": {
+      "type": "boolean"
+    },
+    "fencedDivs": {
+      "type": "boolean"
+    },
+    "highlight": {
+      "type": "boolean"
+    },
+    "inlineFootnotes": {
+      "type": "boolean"
+    },
+    "math": {
+      "type": "boolean"
+    },
+    "superscript": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "report": {
+      "additionalProperties": {},
+      "properties": {
+        "diagnostics": {
+          "items": {},
+          "type": "array"
+        },
+        "schemaVersion": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "sourceFormat": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "schemaVersion",
+        "sourceFormat",
+        "diagnostics"
+      ],
+      "type": "object"
+    },
+    "value": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "report"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the operation read-only and non-destructive. The description adds a behavioral nugget beyond that: the migration comes with 'version 2 fidelity diagnostics,' implying the output or result includes a fidelity assessment. It does not spell out how diagnostics are returned, but the output schema exists and there is no contradiction with the annotations.

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?

One tightly written sentence front-loads the action and target, and the diagnostic qualifier is placed at the end. There is no filler or restatement of schema details.

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

Completeness3/5

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

Given the nested markdownDialect option and an output schema, the description is adequate for basic invocation but leaves at least one use-case gap: it never explains the diagnostic concept or how this tool compares with carve_parse/carve_render/carve_format. An agent can call it from the schema but cannot fully contextualize the result.

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?

The prose names the four format enum values but adds no meaning beyond the schema, and it is silent on the required source parameter's size constraint and the optional markdownDialect semantics. With schema coverage at 67%, the description does not compensate for the remaining 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?

Description uses a specific verb ('Migrate'), names the target ('Carve'), and enumerates the accepted source formats, making the tool's job unmistakable. The operation is clearly distinct from sibling AST-patch, parse, format, and lint tools even without naming them.

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?

The intended use is implied: use this when converting HTML, Markdown, Djot, or BBCode into Carve. However, there is no explicit when-to-use guidance, no named alternatives, and no mention of when the markdownDialect option is appropriate, so the agent must infer boundaries.

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

Deploy Server