fuast

Get a preview's claim link

get_claim_link

Read-only

For a preview that deploy_app deployed without an account: returns the claim link to give to the person, the preview link, and when the preview is deleted if nobody claims it. Opening the claim link and signing in makes the app theirs.

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": {
      "edit_token": "<edit_token>"
    },
    "name": "get_claim_link"
  }
}

Input Schema

Name	Required	Description	Default
`edit_token`	Yes	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
`status`	Yes
`claim_url`	Yes
`deploy_id`	No
`expires_at`	Yes
`preview_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/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 useful behavior — the claim link is meant to be handed to a person, and ignoring it results in the preview being deleted. It does not disclose the sensitivity of the edit_token or any rate/expiry details beyond 'when the preview is deleted', which the schema partially covers.

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, no padding, with the qualifying condition placed first so the agent can rule itself in or out immediately. The second sentence explains the consequence of the action rather than restating the first.

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 the description does not need to enumerate return fields, and annotations cover the read-only profile. What remains slightly under-specified is the lifecycle of the claim link itself (expiry, whether it can be reissued), though for a read-only lookup of this simplicity the definition is close to complete.

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?

Only one parameter, and the schema documents it at 100% coverage including the secret-handling warning. The description reinforces that the token comes from a no-account deploy_app call, but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('returns the claim link'), scopes it to one exact situation ('a preview that deploy_app deployed without an account'), and ties it to the sibling tool that creates the precondition. An agent can distinguish this from get_app or share_app 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?

The precondition for use is stated plainly: only for previews deployed by deploy_app without an account. It does not name an alternative or say what to do for previews created with an account, so it falls short of full when/when-not routing, but the context is unambiguous.

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?