fuast

Get an app's status

get_app

Read-only

Returns one app: URL, status, sharing, handlers, recent deploys with their ids (for rollback_app), today's usage and limits, and the names (never the values) of its env vars.

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

Input Schema

Name	Required	Description	Default
`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.
`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
`url`	Yes
`name`	No
`slug`	Yes
`owner`	No
`usage`	No
`status`	Yes
`deploys`	No
`env_keys`	No
`manifest`	No
`claim_url`	No
`trust_url`	No
`unclaimed`	No
`can_manage`	No
`expires_at`	No
`restricted`	No
`visibility`	No
`preview_url`	No
`shared_with`	No
`trust_command`	No
`last_deploy_at`	No
`require_sign_in`	No
`restricted_hint`	No
`active_deploy_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: env vars are returned as names only, never values, and deploy ids are supplied for use with rollback_app. It omits that some apps require the secret edit_token for access, which is left entirely to 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?

A single front-loaded sentence with no filler; each listed item is meaningfully distinct. It is long and list-like, but nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description needn't recap return values, yet it spends nearly all its text doing so. Meanwhile the routing question (why this rather than check_app/inspect_app) and the edit_token access path go unaddressed, leaving a gap for a read tool with six close siblings.

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%, with both the app slug and the secret edit_token fully documented in the schema itself. The description adds no parameter meaning on top of that, so the baseline of 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?

Opens with a specific verb+resource ("Returns one app") and enumerates exactly what comes back (URL, status, sharing, handlers, deploys, usage, env var names), which is more than a restatement of the title. It does not, however, distinguish itself from near-siblings like check_app, inspect_app, or get_app_source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusions versus alternatives; the agent must infer that this is the general-purpose status read and that check_app/inspect_app/get_app_source do something narrower. The only routing hint is incidental — that deploy ids here feed rollback_app.

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?