Skip to main content
Glama
Sign In

CloneKit

by ai.clonekit
OverviewDiscussionsAdmin

Get kit details

get_kit
Read-onlyIdempotent

Returns the public details of one published kit by its reference: title, summary, link, mode (read: reference files; run: guided steps), file index and entry file, checks, questions, deliverables, tools, inputs, guardrails, license, creator, ratings and the latest changes. Kits that are not public return not_found.

Input Schema

NameRequiredDescriptionDefault
refYesKit reference, like "@clonekitai/landing-page-design-loop".

Output Schema

NameRequiredDescriptionDefault
refYes
urlYes
modeYes
filesYes
titleYes
accessYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ref / description
      Previous value: -"Kit reference, like \"@francisco/whatsapp-agents\"."New value: +"Kit reference, like \"@clonekitai/landing-page-design-loop\"."
  2. Changed10 schema fields changed
    • changedInput schema / properties / ref / description
      Previous value: -"Kit reference, like \"@francisco/whatsapp-agents\". Get it from search_kits."New value: +"Kit reference, like \"@francisco/whatsapp-agents\"."
    • removedInput schema / properties / version
      Removed value: -{
-  "description": "Leave it out for the published version. \"draft\" (the newest version, drafts and versions in review included) or a version number: only for the kit's creator and CloneKit reviewers.",
-  "maxLength": 20,
-  "pattern": "^(?:draft|\\d+\\.\\d+\\.\\d+)$",
-  "type": "string"
-}
    • addedOutput schema / properties / access
      Added value: +{
+  "enum": [
+    "free",
+    "paid"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / files / items / additionalProperties
      Previous value: -falseNew value: +{}
    • removedOutput schema / properties / files / items / properties / title
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedOutput schema / properties / files / items / required
      Previous value: -[
-  "path",
-  "chars",
-  "title"
-]New value: +[
+  "path",
+  "chars"
+]
    • removedOutput schema / properties / next
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / price_label
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "ref",
-  "title",
-  "version",
-  "mode",
-  "price_label",
-  "files",
-  "next"
-]New value: +[
+  "ref",
+  "title",
+  "version",
+  "url",
+  "mode",
+  "access",
+  "files"
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful behavioral context: only public kits are returned, non-public kits produce not_found, and it enumerates the detail categories returned.

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?

The description is front-loaded with the core action and then lists the returned detail categories. It is somewhat dense, but the enumeration is relevant for understanding what the tool returns, and the not_found caveat is clearly placed.

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?

For a one-parameter read-only lookup with rich annotations and an output schema, the description is complete enough. It covers public-only access, not_found behavior for non-public kits, and the categories of information returned.

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%, and the single ref parameter is already documented with a pattern and example. The description reinforces that retrieval is by reference but adds no additional syntax or format details beyond the schema.

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?

The description uses a specific verb and resource: it returns public details of one published kit by reference. It identifies the scope as a single published kit and lists the returned fields, though it does not explicitly differentiate itself from sibling tools such as get_kit_files or search_kits.

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 “by its reference” and the not_found behavior for non-public kits, so an agent can infer this is for fetching details when the kit reference is already known. However, it does not explicitly say when to use this versus search_kits, get_kit_files, or list_creator_kits.

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