Skip to main content
Glama

Copy as New Automation

mcp_recipe_copy

Copy an automation as a new automation for this shoot.

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": {
      "source_workflow_id": "<source_workflow_id>",
      "board_id": "<board_id>"
    },
    "name": "mcp_recipe_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
board_idYesThe open Shoot Board's board_id, from Open Shoot Board or your context.
source_version_idNo
source_workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description confirms creation of a *new* copy, which is useful, but says nothing about what is duplicated (version, asset bindings), whether the source is left untouched, or permission requirements. Adequate but thin for a duplication operation.

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?

A single tight sentence with the verb and scope front-loaded and no filler. It is efficient, though its brevity contributes to the gaps in other dimensions rather than being a virtue on its own.

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

Completeness2/5

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

This is a four-parameter mutation with 25% schema coverage, no output schema, and no annotations explaining what is created or which optional fields default to what. The description does not fill those gaps, leaving the agent under-informed about how to call it correctly.

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 only 25% – just board_id is documented – so the description is expected to compensate and does not. It never explains that 'name' sets the new copy's title, that source_version_id picks which version to duplicate, or that source_workflow_id identifies the source recipe. Half the parameters remain semantically opaque.

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

Purpose3/5

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

States a clear verb+resource: copying an automation into a new one scoped to this shoot. However, it uses 'automation' where the tool name and siblings use 'recipe', and it does nothing to distinguish itself from mcp_recipe_list, mcp_recipe_open, mcp_recipe_save_draft, or mcp_recipe_preflight. An agent gets the gist but must infer the relationship to those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative. 'For this shoot' hints at context but never states when an agent should duplicate rather than open, edit, or list a recipe. The agent must guess the triggering condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources