Skip to main content
Glama

Recommend Carousel Ideas

carousels_board_ideas
Read-onlyIdempotent

Recommend six carousel ideas from the workspace brand brief, each with a cover hook, angle, goal (grow, convert or both), archetype and why it should perform. Pass one to carousels_board_generate as its prompt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carousels_board_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered elsewhere. The description adds meaningful behavior beyond that: the tool reads the workspace brand brief as its grounding source, returns a fixed batch of six candidates rather than an open-ended list, and structures each candidate around a stated goal taxonomy (grow, convert, both). It does not address cost, latency, or what happens when the brand brief is empty, which keeps it below 5.

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?

Two sentences, both front-loaded with the essential information: the first defines the output, the second defines the next action. There is no filler, and the enumerated idea fields read as a compact spec rather than prose padding.

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

Completeness4/5

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

An output schema exists, so the description need not detail return values, yet it still usefully names the per-idea fields. For a single-parameter, read-only generator tool this is nearly complete; the remaining gap is the unstated precondition that a brand brief must exist in the workspace for meaningful output.

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

Parameters3/5

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

There is a single optional, nullable workspaceId with 0% schema description coverage, so the schema leaves its meaning unclear. The phrase 'from the workspace brand brief' implicitly ties the parameter to the workspace whose brand assets ground the recommendations, which is genuinely useful, but the description never explains why the parameter is optional or what the default scope is when it is omitted.

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?

The description gives a specific verb (recommend), a concrete count (six), the source (workspace brand brief), and enumerates exactly what each idea contains (cover hook, angle, goal, archetype, rationale). That level of output specification makes it immediately distinguishable from carousels_board_generate, which it explicitly names as the downstream step.

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?

The final sentence gives a clear handoff rule: pick one idea and pass it to carousels_board_generate as the prompt, which tells the agent both the position of this tool in the workflow and what to do with the result. It stops short of stating exclusions (e.g., when to skip ideation and edit an existing board instead), so it is strong context rather than a full when/when-not decision rule.

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