ATTIM

Preview version

preview_version

Make a private one-use link to an earlier version. Open it within 60 seconds; it then lasts 15 minutes.

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": {
      "slug": "<slug>",
      "versionId": "<versionId>"
    },
    "name": "preview_version"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`versionId`	Yes

Output Schema

Name	Required	Description	Default
`url`	Yes
`expiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / slug / minLength
```
Removed value: -1
```
- removedInput schema / properties / versionId / anyOf
```
Removed value: -[
-  {
-    "pattern": "^[1-9][0-9]*$",
-    "type": "string"
-  },
-  {
-    "minimum": 1,
-    "type": "integer"
-  }
-]
```
- addedInput schema / properties / versionId / type
```
Added value: +"string"
```
- removedOutput schema / properties / slug
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / versionId
```
Removed value: -{
-  "type": "string"
-}
```
First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only flag it as non-read-only, non-destructive and non-idempotent; the description adds genuinely new information the annotations cannot convey — the link is private, single-use, must be opened within 60 seconds, and then lives 15 minutes. It does not state whether the preview shows draft/unpublished state or what authentication the recipient needs, which are the remaining behavioral gaps.

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 compact sentences, zero filler, with the most decision-relevant fact (one-use, expiring link) front-loaded and the timing rules immediately after.

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 returned link need not be explained, and the critical operational constraint (60-second open window, 15-minute lifetime) is fully covered. The only substantive omission is the meaning of the two required inputs, particularly slug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters. 'An earlier version' loosely maps to versionId, but 'slug' is never mentioned and it is unclear whether it identifies the site, the link, or the version being previewed. With zero coverage the description had to carry this and does not.

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?

Specific verb+resource: 'Make a private one-use link to an earlier version' tells an agent exactly what artifact is produced and what it points at. It is clearly distinct from list_versions or download_version, though it never names a sibling to contrast against.

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?

The timing constraint implies the intended use (a quick, shareable peek at a prior version) but there is no explicit statement of when to choose this over download_version or restore_version, and no stated prerequisites or exclusions. Usage must be inferred from the artifact described.

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

All ATTIM 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?