Skip to main content
Glama

GenHTTP Lambda

by dev.genhttp
OverviewDiscussionsAdmin

Create a lambda

create_lambda

Create a lambda. Returns its public address and a private editor key, the only way back in. It starts with version 1 - an empty starter, or a copy of a demo. Nothing is online until deploy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoHow the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer.
templateNoLeft out, the lambda starts empty. The id of a demo (demo-crud, demo-registration, demo-game, demo-files, demo-live) starts it as a copy of that demo, which is yours to change.
publicKeyNoRequested address: lower case letters, digits and dashes. Generated if omitted.
acceptTermsYesMust be true: the user accepts the terms in platform_guide (free shared machine, deployments may be removed, nothing malicious).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "description": "How the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations supply the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description is free to add higher-value context: the private editor key is "the only way back in" (a critical warning), what version it starts at, and that nothing is live until deploy. This goes well beyond the structured hints and is consistent with them.

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?

Four short sentences, front-loaded with the core action and return values, then lifecycle notes. The key warning is stated early and each sentence carries content; 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 creation tool with no output schema, the description covers what is returned (public address, private key), the initial version state, and the deploy gating. It does not spell out auth/permission nuances, but annotations carry the safety profile and acceptTerms covers the terms gate, so the picture is largely complete.

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 the schema already documents all four parameters, including the view modes, demo ids, key format, and the acceptTerms requirement. The description's "empty starter or a copy of a demo" echoes the template parameter but adds no syntax or rules 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.

Purpose4/5

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

States a specific verb and resource ("Create a lambda") and adds scope detail: it returns a public address and private editor key, and starts at version 1 as either an empty starter or a demo copy. It is clearly distinguishable from read_lambda/update_lambda/delete by the create verb, though it does not explicitly name those siblings.

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 (call this when the user wants a new lambda), and the closing note "Nothing is online until deploy" usefully routes the agent to the deploy sibling. But there is no explicit when-to-use/when-not statement or mention of prerequisites tied to the alternatives.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources