Skip to main content
Glama
Sign In

Kadal Deck

by cc.kadal
OverviewDiscussionsAdmin

Find media for a slide

media_search
Read-onlyIdempotent

Search media a deck can use and get each result's ready MDX (paste it into the slide as it is), its credit and a preview URL. Use it whenever a slide wants an icon, emoji, meme or sticker, instead of writing a media URL yourself. Kinds: icon (every free Iconify set), emoji (Fluent, Noto, Noto Animated, Twemoji; set picks one), template (Imgflip's top meme templates and Kadal's own — replace only the captions' text), kadal (Kadal's own library: stickers, GIF loops, meme templates, illustrations, free to use in any Kadal deck), store (Kadal Store's shelf under the Kadal Deck licence: images, icons, stickers, illustrations, patterns and wallpapers — also as slide backgrounds via frontmatter — music, sound effects, video clips, and shaders as Pro backgrounds; storeKinds narrows it; keep each result's credit attributes), and sticker / gif / meme, which here return Kadal's items only. GIFs, stickers and finished memes from KLIPY are not searched by this server: KLIPY must be asked from the person's own machine, so use the local kadal-deck mcp server (media_search) or the web builder's Insert media for those. Read-only; an empty query lists popular or all items.

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": {
      "kind": "<kind>"
    },
    "name": "media_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNofor emoji: the set (default fluent = Fluent 3D)
kindYesicon (Iconify, every free set), emoji (Fluent, Noto, Noto Animated, Twemoji), sticker, gif, meme (finished memes), template (meme templates to caption), kadal (Kadal's own library: stickers, GIF loops, meme templates, illustrations), store (Kadal Store: images, icons, stickers, illustrations, patterns, wallpapers, music, sound effects, video clips and more, free to place in any deck, credited; `storeKinds` narrows it)
limitNohow many results, default 8
queryNowhat to look for, in a few words ("rocket", "mind blown", "ship it"); empty lists popular or all items
storeKindsNofor store: only these kinds (image, icon, sticker, illustration, pattern, wallpaper, music, sfx, video, lottie, model, shader, lut, gif, meme-template)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"icon (Iconify, every free set), emoji (Fluent, Noto, Noto Animated, Twemoji), sticker, gif, meme (finished memes), template (meme templates to caption), kadal (Kadal's own library: stickers, GIF loops, meme templates, illustrations)"New value: +"icon (Iconify, every free set), emoji (Fluent, Noto, Noto Animated, Twemoji), sticker, gif, meme (finished memes), template (meme templates to caption), kadal (Kadal's own library: stickers, GIF loops, meme templates, illustrations), store (Kadal Store: images, icons, stickers, illustrations, patterns, wallpapers, music, sound effects, video clips and more, free to place in any deck, credited; `storeKinds` narrows it)"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "icon",
-  "emoji",
-  "sticker",
-  "gif",
-  "meme",
-  "template",
-  "kadal"
-]New value: +[
+  "icon",
+  "emoji",
+  "sticker",
+  "gif",
+  "meme",
+  "template",
+  "kadal",
+  "store"
+]
    • addedInput schema / properties / storeKinds
      Added value: +{
+  "description": "for store: only these kinds (image, icon, sticker, illustration, pattern, wallpaper, music, sfx, video, lottie, model, shader, lut, gif, meme-template)",
+  "items": {
+    "enum": [
+      "image",
+      "icon",
+      "sticker",
+      "illustration",
+      "pattern",
+      "wallpaper",
+      "music",
+      "sfx",
+      "video",
+      "lottie",
+      "model",
+      "shader",
+      "lut",
+      "gif",
+      "meme-template"
+    ],
+    "type": "string"
+  },
+  "maxItems": 15,
+  "type": "array"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds real context on top: empty `query` lists popular or all items, template results must only have caption text replaced, credits must be preserved, and the store shelf carries a specific licence plus background usage via `frontmatter`. The KLIPY exclusion is a behavioral limit an agent could not infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and output format are front-loaded, which is right, but the middle is a dense run-on that largely re-enumerates the `kind` and `storeKinds` enums already documented verbatim in the schema. The KLIPY caveat and credit/licence rules earn their place; the repeated catalogue lists do not.

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?

With no output schema, the description carries the return-value burden and does: MDX ready to paste, credit, and preview URL per result. Combined with the licence constraints, empty-query behavior, and the KLIPY fallback path, an agent has everything needed to call this and use the results correctly.

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; the description earns above that by disambiguating `kind` values the schema treats near-identically — 'sticker / gif / meme, which here return Kadal's items only' versus `kadal` versus `store` — and by explaining that `set` picks one emoji set and `storeKinds` narrows the store shelf. It does not add format guidance for `limit` beyond the schema default/max.

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 ('Search media a deck can use') and immediately names the deliverable: each result's ready MDX, credit, and preview URL. No sibling tool (deck CRUD, sharing, stats) overlaps, so the boundary is unambiguous without opening the schema.

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?

Explicit when-to-use: 'Use it whenever a slide wants an icon, emoji, meme or sticker, instead of writing a media URL yourself.' It also names the case it does NOT cover (KLIPY GIFs/stickers/finished memes) and routes the agent to the local `kadal-deck mcp` server or the web builder's Insert media instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kadal Deck toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources