Skip to main content
Glama

Kubeez

log_carousel_deck

Scope: generate:media. Record the locked design system of a carousel deck — composition_system (required, e.g. 'The Modernist'), palette, mark_style, card_treatment, recipe, topic — the moment the user approves it, BEFORE generating slide 1. This powers the 'Recent decks by THIS user' anti-repeat section that get_skill('viral-carousel') injects: without the log, every deck starts from zero history and drifts back to the same look. Free — no credits charged. Returns { logged, recent_decks } so you can sanity-check variety across the user's last decks.

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": {
      "composition_system": "<composition_system>"
    },
    "name": "log_carousel_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
recipeNo
paletteNo
mark_styleNo
card_treatmentNo
composition_systemYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a non-destructive, non-open-world write. The description adds genuinely useful context beyond them: it is free (no credits), it prevents history drift, and it returns { logged, recent_decks } for sanity-checking variety. That is solid added value, though nothing is said about duplication behavior for repeated logs of the same deck.

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?

Front-loads the scope and the core instruction, and most clauses (credit cost, return shape, downstream effect) carry real information. The single dense paragraph is slightly overstuffed, but little could be cut without losing guidance.

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, yet the description still usefully names the return shape, and it explains the cost and the consequence of skipping the call. The remaining gap is how to populate the five optional free-text fields, which matters given zero schema coverage.

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 0% across 6 parameters, so the description must carry the semantic load. It only re-lists the property names, flags composition_system as required, and supplies one example value ('The Modernist'); palette, mark_style, card_treatment, recipe and topic get no format or accepted-value guidance.

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?

States a specific verb and resource ('Record the locked design system of a carousel deck') and enumerates the exact fields captured. An agent can immediately tell this apart from generation siblings like generate_media, since it only logs metadata.

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 timing guidance — log 'the moment the user approves it, BEFORE generating slide 1' — which is the key decision point. It also explains the downstream purpose (feeding the anti-repeat 'Recent decks' section), but names no explicit alternative or when-not-to-use 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