fuast

Get an app's source files

get_app_source

Read-only

Returns the source of the app's live deploy as {path: content}, with the deploy id to pass to update_app_files as expected_deploy_id. Large apps return the file list only: ask again with paths for the files you need. Secrets (.env files, env values) are never returned.

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_app_source"
  }
}

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.
`paths`	No	Only return these files. Leave out for every file.
`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
`name`	No
`slug`	Yes
`files`	Yes
`deploy_id`	Yes
`file_list`	Yes
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real behavior beyond the readOnlyHint/openWorldHint annotations: secrets (.env files, env values) are never returned, and large apps degrade to a file-list-only response. The only missing piece is any hint about size thresholds or auth prerequisites for private apps.

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?

Three tight sentences, front-loaded with the return shape, then the caveat, then the security exclusion. No wasted wording.

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?

An output schema exists, so return values needn't be explained; the description still covers the non-obvious behaviors (truncation, secret exclusion, deploy-id handoff) needed to call and chain the tool correctly.

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 rises above it by explaining the path-filter workflow ('ask again with paths') and the purpose of the returned deploy id for update_app_files. It does not describe edit_token usage, but the schema already covers that.

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 the source of the app's live deploy'), the exact return shape ({path: content}), and ties the deploy id to the downstream update_app_files call. An agent can distinguish this from get_app or update_app_files without opening any 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?

Gives concrete usage guidance: large apps return only the file list, so re-ask with 'paths' for the files needed, and the returned deploy id feeds update_app_files. It doesn't explicitly exclude alternatives (e.g. get_app vs this), but the conditional workflow is clear.

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?