Skip to main content
Glama
Sign In
tdmcp

tdmcp

by lucasmaher-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Publish recipe bundle

publish_recipe_bundle
Destructive

Create a versioned recipe bundle with manifest and checksums for CI upload or handoff. Select recipes by ID or include all; avoid overwriting existing artifacts.

Instructions

Write a local, versioned recipe-bundle publish artifact for CI upload or handoff: .recipes.json, tdmcp-recipe-publish.json, and tdmcp-checksums.json. Use recipe_ids for selected recipes or include_all=true for the whole library; overwrite=false protects existing artifacts. This is a filesystem write tool and returns artifact paths, checksum entries, included recipe count, 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_dir": "<out_dir>"
    },
    "name": "publish_recipe_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilesystem-safe bundle name; becomes <name>.recipes.json after sanitization.recipe-bundle
out_dirYesLocal directory where the bundle JSON, publish manifest, and checksum manifest are written.
versionNoSemantic version recorded in the tdmcp-recipe-publish manifest.0.1.0
overwriteNoWhen false, fail if any output artifact already exists; set true to replace them.
recipe_idsNoRecipe ids to include when include_all is false; missing ids are reported in the bundle.
include_allNoWhen true, publish every recipe in the loaded recipe library and ignore recipe_ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.2/5.0
Behavior4/5

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

The description openly discloses that 'This is a filesystem write tool' and explains the overwrite protection behavior, which complements the destructiveHint annotation. It also states what the return value contains (artifact paths, checksums, count, missing ids), adding useful behavioral context beyond the annotations. 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?

The description is compact (three sentences) and front-loads the primary action and purpose. Every sentence contributes value: the output artifact names, the key parameter choices, and the return values. No redundant or filler text.

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's complexity (6 parameters, no output schema, destructive annotations), the description covers all critical aspects: what files are produced, how to select content, the overwrite safeguard, and the return information. It is sufficiently complete for an agent to invoke and interpret results without additional documentation.

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?

With 100% schema description coverage, the baseline is 3. The description adds meaningful cross-parameter semantics by explaining the selection modes (recipe_ids vs include_all) and overwrite behavior, which clarifies how the parameters interact rather than just repeating each field's schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is highly specific: 'Write a local, versioned recipe-bundle publish artifact for CI upload or handoff' and enumerates the exact output files. It clearly states the verb and resource. However, it does not explicitly differentiate itself from sibling 'export_recipe_bundle' or other bundle-related tools, so it misses the sibling-distinction criterion for a 5.

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?

It provides a clear context for use ('for CI upload or handoff') and gives practical guidance on how to select recipes ('Use recipe_ids for selected recipes or include_all=true for the whole library') and protect existing files ('overwrite=false protects existing artifacts'). It does not mention when not to use it or name alternatives, which keeps it from a 5.

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

Deploy Server

Other Tools