Skip to main content
Glama

Prepare Moodboard

prepare_moodboard

Prepare a moodboard with ManyMotions from a creative brief: five distinct visual directions (subject, setting, light, palette, style), each rendered by two image models as square images. Returns the settings and the credits required. Nothing is generated and no credits are spent. No sign-in is needed to prepare. New images from a text brief only: do not use it for uploaded or reference images. Original directions only: no brand logos, artworks or artists named as the style, copyrighted characters or real people; offer an original description instead.

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": {
      "brief": "<brief>"
    },
    "name": "prepare_moodboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesThe creative brief: what the moodboard is for (brand, interior, fashion, event, project), the mood, colors, materials, era and style.

Output Schema

NameRequiredDescriptionDefault
runNo
stateYes
balanceNo
messageYes
outputsNo
projectYes
dashboard_urlYes
credits_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: no credits are spent, no sign-in is required, and the call returns settings plus the credit cost. This is exactly the cost/auth/preview context an agent needs before committing to a paid generation step, and it is consistent with readOnlyHint=false (a prepared object may be created) since the description scopes the claim to generation and billing.

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?

Four dense sentences, front-loaded with purpose and output shape before the constraints. Every clause carries information, though the closing policy sentence stacks several prohibitions and could be marginally tighter.

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?

For a single-parameter preview tool with an output schema, this covers purpose, cost, auth, return shape, and content restrictions. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning by constraining what the brief may contain (original directions only, no brands/artists/real people) — guidance the schema's field description does not cover. It does not add format or length detail, but the schema already handles that.

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?

Names a specific verb+resource (prepare a moodboard), states the exact output structure (five visual directions, two models each, square images), and explicitly draws the boundary against generation ('Nothing is generated'), which cleanly separates it from the sibling generate_result.

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?

Gives explicit when-to-use ('New images from a text brief only') and when-not ('do not use it for uploaded or reference images'), plus content eligibility rules (no logos, named artists, copyrighted characters, or real people). The agent can route between this and the generate/get siblings without inference.

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