Skip to main content
Glama

Generate Carousel Photo

carousels_board_image

Start one AI photo shaped for the board (slide or square) and return its asset: source. The image finishes in the background; place it with carousels_board_edit right away, it appears once ready. Uses image credits.

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": {
      "projectId": "<projectId>",
      "prompt": "<prompt>",
      "shape": "<shape>"
    },
    "name": "carousels_board_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeYes
promptYes
projectIdYesUUID string.
workspaceIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that generation is asynchronous ('finishes in the background'), that the result is referenced as an asset:<id> source, and that the call consumes image credits. These are non-obvious traits an agent needs. It does not cover failure modes such as insufficient credits or invalid prompts.

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?

Three short sentences, front-loaded with the action, then the async/placement consequence, then the cost note. Every sentence adds information and none is redundant.

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 existence of an output schema reduces the burden of explaining return values, and the async behavior is covered. However, for a 4-parameter generation tool with 25% schema coverage, the definition leaves prompt semantics and workspaceId scoping unexplained.

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% (the sole documented field is projectId as 'UUID string.'), so the description must carry the load. It only echoes the shape values already exposed as an enum and says nothing about prompt intent or length limits, projectId, or the optional workspaceId scope.

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?

States a specific verb and resource: 'Start one AI photo shaped for the board (slide or square)'. The shape distinction and the explicit hand-off to carousels_board_edit separate it from the editing sibling, though the distinction from generation_image_create is not addressed.

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?

Gives clear operating context: call this first, then 'place it with carousels_board_edit right away, it appears once ready.' That is a concrete workflow instruction naming the alternative to use downstream. No explicit when-not-to-use condition, so not a 5.

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