Skip to main content
Glama

Fileion

List versions of a title

list_versions
Read-onlyIdempotent

The published versions of one software title on Fileion, newest first (10 per page): version, platform, release date, file hashes and "N of 5 checks passed", each with its Fileion page address.

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

NameRequiredDescriptionDefault
pageNoPage number, from 1.
slugYesThe title's slug, as search_software returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, not open-world), and the description adds genuinely useful behavior: results are ordered newest first, capped at 10 per page, and include a 'N of 5 checks passed' signal plus per-version page addresses. It does not say how to detect the final page or what an unknown slug yields, so it stops short of full disclosure.

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?

A single dense sentence with the resource and ordering front-loaded and the return fields enumerated in a compact colon list. Every clause carries information; nothing is redundant with the schema or annotations.

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 no output schema, the description carries the job of describing the response and does it well by naming the returned fields and the checks-passed metric. The one gap for a paginated list tool is the absence of guidance on terminating pagination or expected result volume.

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?

Schema coverage is 100%, so slug and page are already documented. The description still adds meaning by stating the page size of 10, which lets the agent reason about the page parameter rather than guessing, though it adds nothing about page bounds or total-count behavior.

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?

Names the exact resource (published versions of one software title), the ordering (newest first) and the returned fields (version, platform, release date, file hashes, checks passed, page address). An agent can tell this apart from get_software (which returns the title itself) without opening the schema.

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: it is obviously the tool for enumerating a title's releases once you have its slug. There is no explicit when-to-use, no exclusions, and no routing to alternatives such as get_software or check_download_link, leaving the agent to infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources