fuast

Read an app's logs

get_logs

Read-only

Returns recent log entries of an app, oldest first: what its handlers wrote with ctx.log, handler errors with stack traces, and platform events such as deploys. Pass the returned cursor as since to read only newer entries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_logs"
  }
}

Input Schema

Name	Required	Description
`app`	No	The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
`level`	No	Lowest level to return. Default info.
`limit`	No	Most entries to return. Default 50.
`since`	No	Cursor from an earlier call: only entries after it.
`edit_token`	No	The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.

Output Schema

Name	Required	Description	Default
`slug`	No
`cursor`	Yes
`entries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-structured behavior: chronological ordering, the three categories of entries surfaced, and the cursor-based incremental read loop. It doesn't discuss volume/rate characteristics, but the added context is substantive.

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 sentences, both load-bearing: the first establishes what comes back and in what order, the second establishes the pagination idiom. Nothing is redundant and the substantive content is front-loaded.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description is sufficient for a read-only log fetcher. The one soft gap is that `app` is not required in the schema but the description speaks as if an app is always targeted, leaving the default scope ambiguous.

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 goes beyond the schema's bare 'Cursor from an earlier call' by explaining the workflow semantics of `since` — feed it the previously returned cursor to fetch only newer entries. Filtering by level and app are only implied, but the key parameter's intent is clarified.

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 ('Returns recent log entries of an app') and then enumerates exactly what is returned: ctx.log output, handler errors with stack traces, and platform events like deploys. Ordering ('oldest first') is specified, which makes it clearly distinguishable from siblings such as get_app or inspect_app.

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 an explicit usage pattern for incremental polling: 'Pass the returned cursor as since to read only newer entries.' That is a real when/how-to-use cue. It does not name an alternative tool or state when not to use this one, so it falls short of a full 5.

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

All fuast 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.

Resources

Need Help?