Skip to main content
Glama

Fileion

Get a software title

get_software
Read-onlyIdempotent

Details of one software title from Fileion: publisher, category, license, platforms and the latest version on each platform, with the 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": "get_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe title's slug, as search_software returns it, e.g. "vlc-media-player".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and closed-world behavior, so that burden is lightened. The description adds a concrete inventory of what the response contains — a useful substitute given no output schema exists. It does not cover failure behavior for an unknown slug, which keeps it below a 5.

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 front-loaded sentence that opens with the core action and then enumerates the payload; every clause carries information and there is no filler or repetition of the title.

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?

For a single-parameter lookup with full annotation coverage, the description plus schema supply everything needed to invoke it correctly, and the field enumeration compensates for the missing output schema. Only the unknown-slug/error case is left unstated.

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 description coverage is 100%; the slug parameter is documented with maxLength and a concrete example ("vlc-media-player"). The description adds no further parameter meaning, so the baseline of 3 for a fully documented schema 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?

The description names a specific verb and resource ("Details of one software title") and enumerates the returned fields (publisher, category, license, platforms, latest version per platform, page address). The word "one" implicitly sets it apart from the broader search sibling, but no sibling is named in the description itself, so the differentiation is weaker than a 5 requires.

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: "one software title" plus the required slug signals a single-record lookup, and the schema's slug description points to search_software as the source of slugs. The description never explicitly states when to use this versus search_software or list_versions, so guidance must be inferred.

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