Skip to main content
Glama
Sign In

CloneKit

by ai.clonekit
OverviewDiscussionsAdmin

Search kits

search_kits
Read-onlyIdempotent

Searches CloneKit's public catalog of kits by keywords, tool ids or area of work. Returns matching public kits ranked by relevance: reference, title, summary, link, creator, the tools each kit uses, whether it is free or paid, and ratings. When no kit matches the keywords, closest lists up to 3 nearby kits. example: true marks sample kits made by CloneKit to show the format.

Input Schema

NameRequiredDescriptionDefault
qNoKeywords describing the task or result, like "landing page design".
limitNoNumber of kits per page (default 20, maximum 50).
queryNoSame as q.
toolsNoTool ids every returned kit uses, like ["vercel", "supabase"].
cursorNonext_cursor from the previous page of results.
domainNoArea of work.

Output Schema

NameRequiredDescriptionDefault
kitsYes
countYes
closestNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from the previous page, to get more results. There is no next_cursor on the last page."New value: +"next_cursor from the previous page of results."
    • changedInput schema / properties / limit / description
      Previous value: -"How many kits (default 20, at most 50)."New value: +"Number of kits per page (default 20, maximum 50)."
    • changedInput schema / properties / q / description
      Previous value: -"What the user wants to get done, in their words."New value: +"Keywords describing the task or result, like \"landing page design\"."
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Same as q.",
+  "maxLength": 200,
+  "type": "string"
+}
    • changedInput schema / properties / tools / description
      Previous value: -"Tool ids the kit must use, like [\"vercel\", \"supabase\"]."New value: +"Tool ids every returned kit uses, like [\"vercel\", \"supabase\"]."
    • removedInput schema / properties / tools / examples
      Removed value: -[
-  [
-    "whatsapp"
-  ],
-  [
-    "vercel",
-    "supabase"
-  ]
-]
    • addedOutput schema / properties / closest / items / properties / access
      Added value: +{
+  "enum": [
+    "free",
+    "paid"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / closest / items / properties / mode
      Added value: +{
+  "enum": [
+    "read",
+    "run"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / closest / items / properties / price_label
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / closest / items / properties / summary
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / closest / items / properties / url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / closest / items / required
      Previous value: -[
-  "ref",
-  "title",
-  "price_label"
-]New value: +[
+  "ref",
+  "title",
+  "url",
+  "summary",
+  "mode",
+  "access"
+]
    • addedOutput schema / properties / kits / items / properties / access
      Added value: +{
+  "enum": [
+    "free",
+    "paid"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / kits / items / properties / mode
      Added value: +{
+  "enum": [
+    "read",
+    "run"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / kits / items / properties / price_label
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / kits / items / properties / summary
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / kits / items / properties / url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / kits / items / required
      Previous value: -[
-  "ref",
-  "title",
-  "price_label"
-]New value: +[
+  "ref",
+  "title",
+  "url",
+  "summary",
+  "mode",
+  "access"
+]
    • removedOutput schema / properties / next
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / next_cursor / description
      Removed value: -"Pass as cursor with the same search filters; absent on the final page."
    • changedOutput schema / required
      Previous value: -[
-  "count",
-  "kits",
-  "next"
-]New value: +[
+  "count",
+  "kits"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavior: results are ranked by relevance, a no-match query falls back to a 'closest' list of up to 3 kits, and 'example: true' flags CloneKit-authored sample kits — details an agent could not derive from the annotations.

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?

Three front-loaded sentences: capability first, then return shape, then edge-case semantics. Dense but every clause carries information; the return-field enumeration is slightly redundant given an output schema exists.

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?

Covers capability, result ranking, fallback behavior, and the sample-kit flag, which is what an agent needs to call and interpret it. Return fields are re-listed despite an output schema, and pagination via limit/cursor is left to the schema, but nothing critical is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The description maps its three matching facets to parameters but adds no syntax, format, or interaction detail beyond what the schema already documents (e.g., that 'query' duplicates 'q', how 'limit' and 'cursor' paginate together).

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 ('Searches') and resource ('CloneKit's public catalog of kits') plus the three matching facets (keywords, tool ids, area of work). The 'public catalog' scope distinguishes it from get_kit (single kit by id) and list_creator_kits (creator-scoped listing) without needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the search framing: call it when you have keywords, tool ids, or a domain and don't already know the kit id. It never explicitly says when to prefer get_kit or list_creator_kits instead, nor does it state any prerequisites, so guidance remains inferential.

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

All CloneKit toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources