Skip to main content
Glama
Sign In

GenHTTP Lambda

by dev.genhttp
OverviewDiscussionsAdmin

Check that code compiles

check_code
Read-onlyIdempotent

Compile without saving or deploying; returns diagnostics with file and line. Does not build the handler, so deploy can still refuse a route whose return type cannot be served.

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

Input Schema

NameRequiredDescriptionDefault
filesYeslambda.cs first. The .cs files of the code are compiled, in any folder; nothing else is - send those, the rest may be left out.
privateKeyYesThe editor key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"lambda.cs first."New value: +"lambda.cs first. The .cs files of the code are compiled, in any folder; nothing else is - send those, the rest may be left out."
    • addedInput schema / properties / files / items / properties / encoding / default
      Added value: +null
    • changedInput schema / properties / files / items / properties / encoding / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / files / items / properties / name / description
      Previous value: -"The .cs files of the code are compiled, in any folder; nothing else is - send those, the rest may be left out."New value: +"lambda.cs and every other .cs file, in any folder, are compiled; 'resources/...' is read and served ('resources/web/app.js'); anything else is code kept with the version, never compiled or served - 'docs/...' and 'tests/...' are the documentation and the tests."
  2. Changed2 schema fields changed
    • changedInput schema / properties / files / items / properties / encoding / description
      Previous value: -"'base64' for binary assets; omit otherwise."New value: +"'base64' for binary files; omit otherwise."
    • changedInput schema / properties / files / items / properties / name / description
      Previous value: -".cs files are compiled; files under .lambda/ - documentation, tests, the build folder - are never compiled; anything else is an asset."New value: +"The .cs files of the code are compiled, in any folder; nothing else is - send those, the rest may be left out."
  3. Changed1 schema field changed
    • changedInput schema / properties / files / items / properties / name / description
      Previous value: -".cs files are compiled; files under .lambda/ are documentation and tests and never compiled; anything else is an asset."New value: +".cs files are compiled; files under .lambda/ - documentation, tests, the build folder - are never compiled; anything else is an asset."
  4. Changed1 schema field changed
    • changedInput schema / properties / files / items / properties / name / description
      Previous value: -".cs files are compiled; anything else is an asset."New value: +".cs files are compiled; files under .lambda/ are documentation and tests and never compiled; anything else is an asset."
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation, and the description adds useful behavioral detail beyond them: it returns file/line diagnostics and does not build the handler, so deploy can still reject some routes. That limitation is important context. It does not cover auth expectations or diagnostic format in depth, but it goes meaningfully beyond the annotations.

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?

Two tight sentences, front-loaded with the core action and scope, followed by the one limitation that matters. No 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 two-parameter compile-check tool with no output schema, the description covers purpose, side-effect scope, return shape at a high level, and a key limitation. It could say a bit more about diagnostic structure or success behavior, but it is complete enough to call correctly.

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%, and the schema itself richly explains 'files' and 'privateKey'. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate.

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 ('Compile') and immediately scopes it as a dry run ('without saving or deploying'), which separates it from write_code and deploy. It also says what it returns ('diagnostics with file and line'), so an agent can identify the tool 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 Guidelines4/5

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

The phrase 'without saving or deploying' gives clear usage context: use this to validate code before persisting or deploying. It does not explicitly name alternatives or state when not to use it, but the intended role is easy to infer.

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