AIfra — temporary static previews

get_preview_status

Read-only

Read current public status, URL and server-enforced expiry of an existing preview. Only the service owner can manually extend expiry; updates never extend it.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "get_preview_status"
  }
}

Input Schema

Name	Required	Description	Default
`preview_id`	Yes	Existing preview_id returned by AIfra. Do not invent it or pass a URL, alias, management key or source IP.

Output Schema

Name	Required	Description
`url`	Yes	Public viewer URL; share only after successful browser confirmation.
`bytes`	Yes
`status`	Yes
`expires_at`	Yes	Server-enforced expiry, normally 48 hours from publication. Updates never extend it; only the owner can manually set a later date.
`preview_id`	Yes	AIfra preview identifier; never a management key.
`files_count`	Yes
`ttl_seconds`	Yes	Remaining seconds at response time, not a new lifetime.
`updates_count`	Yes
`active_slots_limit`	No
`active_slots_for_ip`	No	Aggregate active-slot count, never the source IP.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

addedInput schema / properties / preview_id / description

Added value: +"Existing preview_id returned by AIfra. Do not invent it or pass a URL, alias, management key or source IP."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "active_slots_for_ip": {
+      "description": "Aggregate active-slot count, never the source IP.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "active_slots_limit": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "bytes": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "expires_at": {
+      "description": "Server-enforced expiry, normally 48 hours from publication. Updates never extend it; only the owner can manually set a later date.",
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+      "type": "string"
+    },
+    "files_count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "preview_id": {
+      "description": "AIfra preview identifier; never a management key.",
+      "pattern": "^pv_[A-Za-z0-9_-]{24}$",
+      "type": "string"
+    },
+    "status": {
+      "const": "ready",
+      "type": "string"
+    },
+    "ttl_seconds": {
+      "description": "Remaining seconds at response time, not a new lifetime.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "updates_count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "url": {
+      "description": "Public viewer URL; share only after successful browser confirmation.",
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "preview_id",
+    "status",
+    "url",
+    "expires_at",
+    "ttl_seconds",
+    "bytes",
+    "files_count",
+    "updates_count"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only and open-world safety, but the description adds real behavioral context beyond them: that only the service owner can manually extend expiry and that updates never extend it, which tells the agent reading status is the reliable way to observe expiry. It does not cover error behavior when the preview_id is unknown or invalid.

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?

Two tight sentences with the returned fields front-loaded and no filler. The second sentence is slightly tangential to invocation but earns its place by clarifying the expiry lifecycle.

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?

With an output schema present, return values need no explanation, and annotations handle the safety profile. The description covers purpose plus the non-obvious expiry rule; the only gap is the lack of explicit routing against status-like siblings such as get_operation_status.

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 schema description coverage is 100%, with the schema itself spelling out the ID format and forbidding URLs, aliases, management keys, or source IPs. The description adds no parameter-level 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?

States a specific verb (Read) and resource (an existing preview), and enumerates exactly what is returned: public status, URL, and server-enforced expiry. This is clearly distinct from create/delete/update siblings, though it does not name any sibling explicitly to route the agent.

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

Usage Guidelines3/5

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

Usage is implied — call this to inspect the current state of an existing preview — but there is no explicit when-to-use guidance, no statement of prerequisites (e.g. that the preview must exist), and no differentiation from get_operation_status, which also sounds like a status reader.

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?