GenHTTP Lambda

Switch on a kind of data

enable_data

DestructiveIdempotent

Switch on a kind of data the lambda needs and does not have: 'database' (a SQLite database for its records - off until switched on, which makes it, empty), 'secrets' (off until switched on) or 'workspace' (on unless the owner switched it off). Do it when what you build needs it - records need the database, an API key for a service it calls needs secrets. Takes effect at once, without a deploy; switching the database on starts the lambda again on its next request, so its migrations run. There is no tool to switch one off: that deletes what it held, and is the owner's to do in the editor.

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

Input Schema

Name	Required	Description	Default
`kind`	Yes	Which kind.
`privateKey`	Yes	The editor key.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / kind / description

Previous value: -"Which kind: 'database' or 'workspace' or 'secrets'."New value: +"Which kind."

addedInput schema / properties / kind / enum

Added value: +[
+  "database",
+  "secrets",
+  "workspace"
+]

AddedSep 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond annotations: immediate effect without deploy, lambda restart on next request so migrations run, database initially empty, and no off tool because disabling deletes data. Minor gap: it does not explicitly reconcile the destructiveHint with the enabling action or discuss failure/auth behavior.

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?

Front-loads the three kinds and then follows with when-to-use and operational consequences; every sentence adds value. The first sentence is dense with parentheticals, which slightly hurts scanability.

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 the key behavioral context an agent needs for a mutation tool: effect timing, restart/migration side effect, initial state, and why no disable tool exists. It leaves return/response and authentication expectations unstated, but annotations and the fully covered schema fill most of that.

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 both parameters are documented, and the description adds meaningful semantics for the 'kind' enum by explaining each option's state and purpose. It adds nothing for privateKey beyond the schema's 'editor key,' so not a 5.

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-resource pair ('Switch on a kind of data') and enumerates the three data kinds with their initial states. It distinguishes the operation from sibling read/write tools by framing it as enabling lambda data and notes that no disable tool exists.

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?

Gives concrete conditions ('when what you build needs it') with examples (records need database, API key needs secrets) and explicitly routes disabling to the owner/editor. This tells the agent when to call it and prevents it from searching for an off-tool.

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

All GenHTTP Lambda tools Inspect

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.