GenHTTP Lambda

Read a lambda's logs

read_logs

Read-onlyIdempotent

What a deployed lambda has been doing: its recent requests and how they were answered, what it printed, the errors it threw with their stack traces, and how much traffic it has had in the last hour and day. With feature, what that feature's preview has been doing instead, kept apart from the lambda's visitors. Call it after deploying to see that it works, and first when something is reported broken.

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": "read_logs"
  }
}

Input Schema

Name	Required	Description	Default
`level`	No	The lowest level worth reading: 'info' for everything, 'warn' for problems, 'error' for failures.	info
`limit`	No	At most this many lines, the newest.
`since`	No	The cursor a previous call answered with, to read only what is new since then.
`feature`	No	Read what this feature's preview did instead.
`privateKey`	Yes	The editor key, or the key of a demo.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 2, 2026

addedInput schema / properties / level / default
```
Added value: +"info"
```

changedInput schema / properties / level / description

Previous value: -"The lowest level worth reading: 'info' for everything, 'warn' for problems, 'error' for failures. Left out, 'info'."New value: +"The lowest level worth reading: 'info' for everything, 'warn' for problems, 'error' for failures."

addedInput schema / properties / level / enum

Added value: +[
+  "debug",
+  "info",
+  "warn",
+  "warning",
+  "error"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```

changedInput schema / properties / limit / description

Previous value: -"At most this many lines, the newest. Left out, 100."New value: +"At most this many lines, the newest."

addedInput schema / properties / limit / maximum
```
Added value: +1000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```
addedInput schema / properties / since / default
```
Added value: +0
```

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / feature

Added value: +{
+  "description": "Read what this feature's preview did instead.",
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value by disclosing the content shape (requests/answers, prints, error stack traces, traffic over the last hour and day) and that feature-preview activity is kept separate from the lambda's visitors. It does not discuss retention beyond the stated windows or cursor semantics, which are covered in the schema.

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-loaded with the content inventory, followed by the feature-mode clarification and then the usage guidance. Dense but every clause carries information; the long enumeration of what is returned is justified because no output schema exists.

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, so the description must convey return contents — it does so well (requests, prints, stack traces, traffic windows), and the cursor/limit/level mechanics live in the fully documented schema. The only gap is not stating how level, limit, and time windows interact in the response, but nothing essential for a correct call is missing.

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 the baseline is 3. The description adds meaning beyond the schema for the `feature` parameter by clarifying that preview activity is 'kept apart from the lambda's visitors' — isolation semantics the schema's one-liner doesn't convey. The other parameters are left to their already-thorough schema descriptions.

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 (read a deployed lambda's logs) and enumerates exactly what is returned: recent requests and their answers, printed output, errors with stack traces, and hourly/daily traffic. It also distinguishes the alternate mode (feature preview logs kept apart from the lambda's visitors), which separates it from read_lambda (config) and analytics (traffic metrics).

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?

Gives two concrete usage moments: 'after deploying to see that it works' and 'first when something is reported broken,' which tells the agent it is a diagnostic entry point. It does not explicitly name alternatives like analytics or read_lambda, so routing is implied rather than spelled out.

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.