Skip to main content
Glama

Fileion

Compare software titles

compare_software
Read-onlyIdempotent

Compare 2 to 4 software titles from Fileion side by side: publisher, license, platforms, latest versions, pros, cons and key features, plus the feature rows Fileion editors checked by hand (yes, partly or no, with the date). Gives the Fileion "A vs B" page when the first two have one.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes2 to 4 title slugs, as search_software returns them, e.g. ["google-chrome", "mozilla-firefox"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety profile is covered. The description adds genuine behavioral detail beyond that: the editor-verified feature rows and the fact that an 'A vs B' page is returned when one exists for the first two titles. It does not explain what happens when no curated page exists, or the response shape.

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 sentences, front-loaded with the core action and the comparison scope, with the payoff and special-case behavior last. The field list is dense but each item is informative; slight bloat from the nested quote formatting but no filler sentences.

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 read-only tool with no output schema, the description is nearly sufficient: it names the comparison dimensions, the 2-4 bound, slug source, and the conditional 'A vs B' page. Only the return structure and the no-curated-page case are left unstated, which is minor here.

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% and already documents the 2-4 slug constraint with an example, so baseline would be 3. The description reinforces the count range and clarifies slug provenance ('from Fileion', as search_software returns them) and the special role of the first two slugs, which is meaning the schema does not encode.

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?

States a specific verb and resource ('Compare 2 to 4 software titles ... side by side') and enumerates exactly what is compared: publisher, license, platforms, versions, pros, cons, features, plus editor-checked feature rows with dates. This distinguishes it clearly from get_software (single title), search_software (discovery), and list_versions (versions only).

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?

Implicitly scopes usage to multi-title comparison of 2-4 items and hints that slugs come from search_software, but it never states when to prefer this over calling get_software per title, nor when to stop at 2 vs extend to 4. No exclusions or prerequisites are given beyond the slug source.

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