ATTIM

List versions

list_versions

Read-onlyIdempotent

List a site's last 10 versions, with their names and which one is live.

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>"
    },
    "name": "list_versions"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`versions`	Yes
`currentVersionId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / slug / minLength
```
Removed value: -1
```
- removedOutput schema / properties / slug
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / versions / items / properties / fileCount
```
Removed value: -{
-  "type": "integer"
-}
```
- removedOutput schema / properties / versions / items / properties / finalizedAt
```
Removed value: -{
-  "type": "string"
-}
```
First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds non-obvious behavior: results are capped at 10 versions and include the live indicator, which tells the agent the list is truncated and not exhaustive.

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?

One sentence with no filler; the cap of 10 and the live flag, the two facts that matter for interpretation, are front-loaded.

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

Completeness5/5

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

For a one-parameter read tool with an output schema and full annotation coverage, nothing essential is missing; the description need not describe return shapes or pagination.

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 coverage is 0%, so the description must carry the single slug parameter, and it only implies that slug identifies the site without stating format or whether it is a site ID or subdomain. Partial compensation keeps this at the minimum viable level.

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 and resource (list a site's versions) plus scope detail: the last 10, with names and which is live. That distinguishes it reasonably from mutation siblings like publish_version or restore_version, though no sibling is named explicitly.

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 only implied by the read-only framing; there is no statement of when to pick this over preview_version, download_version, or restore_version, nor any prerequisite about the site needing to exist.

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?