tdmcp

Import recipe bundle

import_recipe_bundle

Destructive

Import recipes from a portable JSON bundle into a recipe directory, validating each recipe before writing to prevent corruption.

Instructions

Import recipes from a portable JSON bundle into a recipe directory. The inverse of export_recipe_bundle: each recipe is validated before it is written, so a malformed bundle fails loudly instead of corrupting the directory. Writes files (destructive).

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": {
      "bundle_file": "<bundle_file>",
      "out_dir": "<out_dir>"
    },
    "name": "import_recipe_bundle"
  }
}

Input Schema

Name	Required	Description	Default
`out_dir`	Yes
`overwrite`	No
`bundle_file`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description adds the validation behavior: each recipe is validated before write, so a malformed bundle fails loudly instead of corrupting the directory. This is useful behavioral context. The final sentence reinforces the destructive nature already noted in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences and front-loads the core purpose. The last sentence ('Writes files (destructive)') is somewhat redundant with the destructiveHint annotation, but overall the description is concise and without unnecessary fluff.

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?

The description covers purpose, validation, and destructive behavior, but it lacks details on the overwrite parameter's behavior and any return value. Given the sparse schema and absence of an output schema, a bit more explanation of these operational aspects would make it complete.

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 description coverage is 0%, and the description only indirectly maps 'bundle' to bundle_file and 'directory' to out_dir. The optional 'overwrite' parameter is not mentioned at all, leaving the agent without guidance on its semantics or the consequences of setting it true.

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 clearly states the tool imports recipes from a portable JSON bundle into a recipe directory. It explicitly identifies the inverse relationship with export_recipe_bundle, which differentiates it from sibling tools.

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 names export_recipe_bundle as the counterpart, giving clear context for when to use this tool. It also implies limitations by specifying 'portable JSON bundle', which separates it from URL-based imports, though it doesn't explicitly list exclusions.

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

Deploy Server