tdmcp

Export recipe bundle

export_recipe_bundle

Destructive

Export recipes to a portable JSON bundle for transferring between machines. Choose specific recipes or export the full library, with missing IDs reported.

Instructions

Write a portable JSON recipe bundle to out_file. When include_all=false, recipe_ids selects the entries; when include_all=true, the full local library is exported and recipe_ids is ignored. Unknown IDs are reported in missing rather than silently substituted. Use import_recipe_bundle to restore the bundle on another machine or publish_recipe_bundle when you need checksums/versioned handoff artifacts. This writes a local file and returns the bundle kind, version, timestamp, exported recipes, and missing IDs.

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": {
      "out_file": "<out_file>"
    },
    "name": "export_recipe_bundle"
  }
}

Input Schema

Name	Required	Description
`out_file`	Yes	Destination path for the portable recipe-bundle JSON file.
`recipe_ids`	No	Recipe IDs to export when include_all=false; unknown IDs are listed in missing.
`include_all`	No	Export the complete local recipe library when true; otherwise export recipe_ids only.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`missing`	Yes
`recipes`	Yes
`version`	Yes
`exported_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=true), the description adds meaningful behavioral details: unknown IDs are reported in missing rather than silently substituted, and the return payload includes bundle kind, version, timestamp, exported recipes, and missing IDs. No contradiction with 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?

Four sentences, front-loaded with the core purpose, and every sentence earns its place: purpose, behavior, sibling alternatives, and return value. No fluff or redundancy.

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?

Given the tool has a rich schema, annotations, and an output schema, the description is still self-contained: it covers the main action, the include_all/recipe_ids interaction, unknown ID behavior, alternatives, and return fields. Nothing critical is missing.

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

Parameters3/5

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

Schema coverage is 100% with clear per-parameter descriptions, so the baseline is 3. The description adds the conditional relationship (include_all=true ignores recipe_ids) and the unknown-ID handling, but these are largely implied by the schema's own descriptions, providing minimal additional value.

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 opens with a specific action, 'Write a portable JSON recipe bundle to out_file,' clearly identifying the verb, object, and destination. It also distinguishes the tool from siblings by naming import_recipe_bundle and publish_recipe_bundle with different use cases.

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?

Explicitly provides when-to-use guidance: 'Use import_recipe_bundle to restore the bundle on another machine or publish_recipe_bundle when you need checksums/versioned handoff artifacts.' It also clarifies the include_all toggle behavior, giving clear context for selecting this tool.

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

Deploy Server