Skip to main content
Glama
Sign In

GenHTTP Lambda

by dev.genhttp
OverviewDiscussionsAdmin

Deploy a version or a feature

deploy
DestructiveIdempotent

Deploy (publish) a saved version so it goes live at its public address - the newest by default. With feature, deploy that feature's files to its own preview address instead, against its copy of the data, leaving the lambda alone. Returns diagnostics on failure, and whatever was online stays online.

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>"
    },
    "name": "deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureNoDeploy this feature to its preview address instead of a version to the lambda's.
versionNoDefaults to the newest.
privateKeyYesThe editor key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / feature
      Added value: +{
+  "description": "Deploy this feature to its preview address instead of a version to the lambda's.",
+  "type": "string"
+}
  3. 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 destructive=true and idempotent=true, so the safety profile is partly covered. The description adds genuinely non-obvious behavior: failed deploys return diagnostics and 'whatever was online stays online', and feature deploys run against their own copy of the data without touching the lambda. It omits any mention of key/permission requirements or what a successful return looks like.

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 tight sentences, front-loaded with the primary version-deploy case before the feature variant. The em-dash asides are slightly dense but every clause carries information; nothing is padding.

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?

No output schema exists, and the description fills the gap by noting diagnostics are returned on failure and the prior state is preserved. For a destructive two-mode tool this is close to sufficient; only preconditions and a hint at the success return shape are 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 coverage is 100%, so all three parameters are already documented, including the version default and the feature override. The description's param-level content ('newest by default', feature deploys to a preview address) largely restates 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (deploy/publish) and its two distinct scopes: a saved version to its public address, or a feature to its own preview address. An agent can tell exactly what the tool acts on. It stops just short of a 5 because it never names or rules out any sibling tool as an alternative route.

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

Usage Guidelines4/5

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

The 'With feature, deploy...' clause gives clear conditional guidance for choosing between the two modes, and 'the newest by default' tells the agent it can omit version. There is no explicit when-not-to-use or prerequisite guidance (e.g. what must exist before deploying).

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

All GenHTTP Lambda 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