AIfra — temporary static previews

get_deploy_instructions

Read-only

Explain remote browser-confirmed AIfra publication of ready static files, limits and current terms.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`inputs`	Yes
`warning`	Yes
`terms_url`	Yes
`transport`	Yes
`management`	Yes	Private browser-local key; never pass it to MCP.
`publication`	Yes
`terms_version`	Yes
`max_extracted_mib`	Yes
`preview_ttl_hours`	Yes
`approval_ttl_seconds`	Yes
`max_active_mib_per_ip`	Yes
`max_active_per_browser_ip`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "approval_ttl_seconds": {
+      "const": 7200,
+      "type": "number"
+    },
+    "inputs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "management": {
+      "description": "Private browser-local key; never pass it to MCP.",
+      "type": "string"
+    },
+    "max_active_mib_per_ip": {
+      "const": 150,
+      "type": "number"
+    },
+    "max_active_per_browser_ip": {
+      "const": 3,
+      "type": "number"
+    },
+    "max_extracted_mib": {
+      "const": 50,
+      "type": "number"
+    },
+    "preview_ttl_hours": {
+      "const": 48,
+      "type": "number"
+    },
+    "publication": {
+      "const": "browser_confirmation_required",
+      "type": "string"
+    },
+    "terms_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "terms_version": {
+      "type": "string"
+    },
+    "transport": {
+      "const": "streamable-http",
+      "type": "string"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "transport",
+    "publication",
+    "terms_url",
+    "terms_version",
+    "inputs",
+    "preview_ttl_hours",
+    "max_active_per_browser_ip",
+    "max_extracted_mib",
+    "max_active_mib_per_ip",
+    "approval_ttl_seconds",
+    "management",
+    "warning"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

C2.7/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 that the response covers 'limits and current terms,' hinting at the content of the returned info, but says nothing about how instructions are scoped to a deployment or any freshness/permission caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, so it is short, but it is packed with undefined terms ('AIfra', 'browser-confirmed publication') and buries the useful payload ('limits and current terms') at the end. Brevity here reflects under-specification rather than efficient structure.

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?

An output schema exists, so return-value detail is not required. For a zero-parameter read-only tool the description is close to sufficient, but the opaque 'browser-confirmed AIfra publication' phrasing leaves the agent unsure what scenario actually triggers it.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool applies. No parameter-level ambiguity is introduced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Explain' is a weak substitute for what is presumably a retrieval of deployment instructions, and the object phrase 'remote browser-confirmed AIfra publication of ready static files' is jargon-dense and does not resolve to a clear resource. It never distinguishes itself from the preview siblings (create/update/delete/get_preview_status), so an agent cannot tell why it would pick this over them.

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 statement, no precondition (e.g., after a preview is ready), and no mention of alternatives despite five related preview tools existing. The agent must guess the workflow position of this tool from the name alone.

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

All AIfra — temporary static previews 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?