Skip to main content
Glama

Fileion

Search software

search_software
Read-onlyIdempotent

Search the Fileion software directory by name. Returns up to 10 titles per page with their platforms and Fileion page address. Modified apps (changed copies of someone else's app) are left out; unofficial ones are listed with their label.

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": {
      "query": "<query>"
    },
    "name": "search_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
sortNoOrder of the results.
queryYesPart of the software name, e.g. "vlc".
categoryNoCategory slug, e.g. "media-players".
platformNoPlatform slug, e.g. "windows", "mac", "linux", "android".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description does add real behavioral detail beyond annotations: a 10-result page cap, the returned fields (platforms and Fileion page address), exclusion of modified apps, and labeling of unofficial ones.

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?

Three tight sentences, front-loaded with the action and then the result shape. The parenthetical explanation of 'modified apps' costs some words but genuinely clarifies an unusual exclusion rule.

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, describing the return set (up to 10 titles, platforms, page address) is necessary and done. Filtering semantics are disclosed. Gaps are modest: total result counts, default sort, and how to page past the first 10 are 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 coverage is 100%, so all five parameters are documented in the schema, including the enum values for sort and examples for category and platform. The description only echoes the name-matching behavior of 'query' and adds nothing about sort, paging, or how category/platform narrow results, so the baseline 3 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?

States a specific verb and resource: 'Search the Fileion software directory by name,' which is clearly distinct from sibling get_software (single lookup) and compare_software. Minor imprecision: it frames the tool as name-only search even though the schema exposes category and platform filters.

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 — an agent can infer this is the discovery/browse entry point versus get_software for a known item, but the description never names an alternative or states when not to use it. No prerequisites or exclusions are given.

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