Skip to main content
Glama
Sign In

BotKelp

by io.github.aiscimi-code
OverviewDiscussionsAdmin

Get component source

get_component
Read-onlyIdempotent

One component's source files, UNRENDERED (EJS markers, not build-ready): inspect only; use purchase_scaffold for real files. Free, 32/day, signed-in account.

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": {
      "component": "<component>"
    },
    "name": "get_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentYesComponent id, or id@version, e.g. "supabase-client@2.0.0".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / account_api_key
      Removed value: -{
-  "description": "BotKelp account key (starts with \"bk_live_\"). Required.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "account_api_key",
-  "component"
-]New value: +[
+  "component"
+]
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real value: a free-tier rate limit (32/day), an auth requirement (signed-in account), and the key output trait that results are unrendered templates. It does not cover what happens when the quota is exhausted or whether a missing component errors versus returns empty, which keeps it off a 5.

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?

One dense sentence with the payload caveat front-loaded and the escape hatch and cost appended; every clause earns its place with zero filler.

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 still characterizes the returned content (EJS markers, not build-ready) and the cost/auth envelope, which is everything an agent needs to call it correctly for a one-parameter read tool.

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 parameter is documented there with an id@version example format. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 ('One component's source files') plus a decisive qualifier, UNRENDERED with EJS markers rather than build-ready output, that separates it from get_scaffold and purchase_scaffold. An agent knows exactly what it gets back 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?

Explicitly scopes use to inspection ('inspect only') and names the alternative for the other intent ('use purchase_scaffold for real files'), so the routing decision is fully determined. The quota and sign-in note further constrains when it can be called.

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