Skip to main content
Glama
BeatAPI

BeatDesign

by BeatAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bdesign_generation_submit

Submit a reviewed Canvas generation node to trigger the provider request, create a visible output node, and retain successful outputs as reusable assets.

Instructions

Submit from a reviewed Canvas generation node. A visible output node is created before the provider request, and successful outputs remain reusable Assets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
promptYes
modelIdYes
commandIdNo
projectIdNo
parametersNo
referencesNo
sourceCardIdYes
idempotencyKeyNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.4
    • changedInput schema / properties / references / items / properties / role / enum
      Previous value: -[
-  "source",
-  "reference",
-  "style",
-  "subject",
-  "pose",
-  "first_frame",
-  "last_frame",
-  "audio_track"
-]New value: +[
+  "source",
+  "reference",
+  "style",
+  "subject",
+  "pose",
+  "audio_track"
+]
  2. First observedv0.2.3

TDQS

C2.7/5.0
Behavior3/5

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

The description adds behavioral context beyond the annotations: it creates a visible output node before the provider request and makes successful outputs reusable assets. It does not contradict the annotations (idempotentHint false, destructiveHint false) but does not disclose failure behavior or retry implications, which would be valuable given idempotency is not guaranteed.

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 concise, two sentences, and front-loads the primary action. However, for a tool with 10 parameters and nested objects, the brevity borders on under-specification rather than effective conciseness.

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?

Given the tool's complexity (10 parameters, nested objects, no output schema), the description is far too thin. It fails to explain what 'reviewed' means, how to obtain sourceCardId, what modes are available, or any workflow context. It is not complete enough for an agent to call it correctly.

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

Parameters1/5

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

With 0% schema description coverage, the description is entirely responsible for parameter semantics, yet it mentions no parameters at all. It provides no guidance on mode, modelId, prompt, references, or any of the 10 parameters, making it impossible for an agent to understand what values to supply without external knowledge.

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 clearly states the action is to submit from a reviewed Canvas generation node, and mentions the creation of a visible output node and reusable assets. It distinguishes itself from status and history tools, though it doesn't explicitly name any sibling it is not.

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?

The description implies a prerequisite ('reviewed Canvas generation node') but provides no explicit guidance on when to use this tool versus alternatives like bdesign_generation_status or bdesign_canvas_apply. There are no when-to-use or when-not-to-use instructions.

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