Skip to main content
Glama
Sign In

BotKelp

by com.botkelp
OverviewDiscussionsAdmin

Purchase scaffold

purchase_scaffold

Buys a CI-green starter repo for component ids (credits via your signed-in account, or x402). Returns a git clone command and projectid. Red builds are refused and not charged. delivery "inline" returns files instead (more tokens).

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": {
      "components": "<components>"
    },
    "name": "purchase_scaffold"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoSaved project metadata.
deliveryNo"clone" (default) or "inline".
maintainNoRenewable repeat access (default true).
componentsYesComponent ids, e.g. ["nextjs-base","tailwind"].
site_profileNotrue or a profile name: bake legal pages in.
admin_page_setNoExtra file-set name.
template_filesNoExtra files: true, or [{name}|{source,dest}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / admin_page_set / description
      Previous value: -"Optional extra file-tree name (same overlay as template_files). Prefer site_profile / template_files."New value: +"Extra file-set name."
    • changedInput schema / properties / components / description
      Previous value: -"Component ids to include, e.g. [\"nextjs-base\", \"tailwind\", \"supabase-client\"]."New value: +"Component ids, e.g. [\"nextjs-base\",\"tailwind\"]."
    • changedInput schema / properties / delivery / description
      Previous value: -"\"clone\" (default): git clone command. \"inline\": files in the reply. No git needed. More tokens."New value: +"\"clone\" (default) or \"inline\"."
    • changedInput schema / properties / maintain / description
      Previous value: -"Keep repeat access to this repo renewable. Defaults to true. Ignored for x402 (accountless) purchases."New value: +"Renewable repeat access (default true)."
    • changedInput schema / properties / project / description
      Previous value: -"Project metadata to save alongside the purchased scaffold."New value: +"Saved project metadata."
    • changedInput schema / properties / project / properties / description / description
      Previous value: -"Free-text description saved with the project."New value: +"Notes."
    • changedInput schema / properties / project / properties / name / description
      Previous value: -"Your label for this project, shown in get_projects and in the purchase reply. Shared template repos keep a generic package name, so this is not written into package.json."New value: +"Your label."
    • changedInput schema / properties / site_profile / description
      Previous value: -"false/omit: skip. true: bake this account's one site profile into the clone (errors if 0 or >1). A string: bake that named profile (privacy, terms, cookies, …)."New value: +"true or a profile name: bake legal pages in."
    • changedInput schema / properties / template_files / anyOf
      Previous value: -[
-  {
-    "const": true,
-    "type": "boolean"
-  },
-  {
-    "items": {
-      "properties": {
-        "dest": {
-          "description": "Destination in the generated project. Defaults to the file's stored path / source path.",
-          "type": "string"
-        },
-        "name": {
-          "description": "Saved dashboard template file name.",
-          "type": "string"
-        },
-        "source": {
-          "description": "Path in the connected GitHub repo, e.g. \"legal/gdpr.md\" or \"app/rules/page.tsx\".",
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "const": true,
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "properties": {
+        "dest": {
+          "description": "Destination path.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Saved file name.",
+          "type": "string"
+        },
+        "source": {
+          "description": "Path in connected repo.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / template_files / description
      Previous value: -"true: every saved dashboard template file. Or a list of {name} and/or {source, dest} from the connected GitHub repo."New value: +"Extra files: true, or [{name}|{source,dest}]."
  2. Changed1 schema field changed
    • changedInput schema / properties / project / properties / name / description
      Previous value: -"Name used for the project and in package.json."New value: +"Your label for this project, shown in get_projects and in the purchase reply. Shared template repos keep a generic package name, so this is not written into package.json."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses payment paths (signed-in credits or x402), refusal and no-charge behavior for red builds, and the return shape (clone command plus projectid). It also notes the token tradeoff for inline delivery, though it does not cover auth prerequisites in detail.

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?

Three short sentences, front-loaded with the core action and return behavior. Every sentence adds useful information without repetition or filler.

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?

For a 7-parameter purchase tool with no output schema, the description covers the essential outputs, billing paths, and failure behavior. It does not explain every optional parameter, but the schema already has full coverage for those details.

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 schema already documents the parameters well. The description adds meaningful context for delivery by explaining that inline returns files instead and costs more tokens, which goes beyond the enum label in 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 states a specific verb and resource: buying a CI-green starter repo for component ids. It is clear what the tool does, but it does not explicitly distinguish purchase_scaffold from sibling tools such as get_scaffold or verify_scaffold.

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 'Buys a CI-green starter repo for component ids,' but the description does not explicitly say when to choose this tool over get_scaffold or verify_scaffold. The delivery-mode note is useful but is not tool-selection guidance.

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

All BotKelp 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