Skip to main content
Glama

GenHTTP Lambda

by dev.genhttp
OverviewDiscussionsAdmin

Read a lambda

read_lambda
Read-onlyIdempotent

A lambda's status (online version, newest version, expiry, its tier and what it may use there), its open features, the recent versions with what each was asked for and changed, its data (the database, the workspace and the secrets: whether each is on, what it holds, and which secrets the code reads that have no value yet), and one version - or, with feature, that feature: its documentation (docs/: what the app is and why, the technical decisions), how it is tested (tests/), and its files. The documentation comes first and in full up to 20,000 characters; the files come in full while they fit into 30,000 characters - the C# first, then the resources, then the rest of the code - and by name and length after that, with file to read one - a test script or its data too. Read the documentation and the history before changing what you did not write. Also how a demo is read: pass its key from list_demos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoReturn only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, 'tests/smoke.mjs' and 'resources/web/index.html' included.
featureNoRead this feature - its files, its base, and which newer versions it would have to take in before it can be merged - instead of a version.
versionNoDefaults to the newest.
privateKeyYesThe editor key, or the key of a demo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / file / description
      Previous value: -"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' and '.lambda/build/README.md' included."New value: +"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, 'tests/smoke.mjs' and 'resources/web/index.html' included."
  2. Changed1 schema field changed
    • changedInput schema / properties / file / description
      Previous value: -"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' included."New value: +"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' and '.lambda/build/README.md' included."
  3. Changed1 schema field changed
    • changedInput schema / properties / file / description
      Previous value: -"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it."New value: +"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' included."
  4. Changed2 schema fields changed
    • addedInput schema / properties / feature
      Added value: +{
+  "description": "Read this feature - its files, its base, and which newer versions it would have to take in before it can be merged - instead of a version.",
+  "type": "string"
+}
    • changedInput schema / properties / file / description
      Previous value: -"Return only this file of the version, in full however large the rest is - up to 1,048,576 characters, beyond which the version's zip has it."New value: +"Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it."
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld=false, and destructive=false. The description adds substantial output behavior beyond those annotations: documentation is returned first up to 20,000 characters, files are returned in a specific order while they fit within 30,000 characters, and the file parameter can return a single file up to 1,048,576 characters before falling back to a zip. Auth and rate-limit behavior are not described, but the return-shaping details are strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense, run-on paragraph of about 170 words. While much of the content is relevant for a tool without an output schema, it is not front-loaded or structured for quick scanning, and many clauses are packed into one unwieldy sentence.

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?

There is no output schema, so the description must explain return values and limits. It comprehensively describes the status, features, versions, data, secrets, documentation, tests, and files that are returned, including ordering and truncation rules. It also covers how demo lambdas are read.

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%, so the input schema already documents all four parameters. The description largely restates file, feature, and version behavior and adds only a small amount of context for privateKey by noting that demo keys come from list_demos. With full schema coverage, this meets the baseline of 3.

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: reading a lambda's status, features, versions, data, and version/feature files. It is clear what the tool does, though it does not explicitly differentiate itself from all sibling read tools such as read_logs or read_database.

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?

The description gives one explicit usage cue: read documentation and history before changing code you did not write. It also notes that demo access uses a key from list_demos. It does not state when not to use this tool or name alternative read tools for other contexts.

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