Skip to main content
Glama

Fileion

Get install commands

get_install_command
Read-onlyIdempotent

The install commands Fileion has for a software title: package-manager commands (winget, Chocolatey, Scoop, Homebrew), silent-install switches, the installer file name and SHA-256, and the Fileion install page. The commands are quoted, never run, and each says where it came from.

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_install_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe title's slug, as search_software returns it, e.g. "vlc-media-player".
platformNoOnly this platform, e.g. "windows" or "mac".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, closed-world), so the description earns credit for adding what annotations cannot: the commands are quoted rather than executed, and each one carries its provenance. Those two facts materially change how an agent should treat the output (safe to display, citations available, not an execution step). It does not cover what happens when no commands exist for a title or how platform filtering affects the result.

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 payload contents and closing with the behavioral caveat. The long colon-delimited list of command sources is dense but each item carries information. Minor cost: the enumeration reads as a run-on and could be tightened.

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 burden of describing returns, and it does so concretely, listing every field family an agent would receive. For a two-parameter read tool with full annotation coverage this is close to complete; the only omission is behavior on empty results or on a platform with no matching commands.

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% and both parameters are documented in-schema with examples, including the cross-reference to search_software for the slug format. The description adds only the framing 'for a software title', which does not extend parameter meaning beyond the schema. 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?

The description enumerates exactly what is returned: package-manager commands for winget/Chocolatey/Scoop/Homebrew, silent-install switches, installer file name and SHA-256, and the install page URL. That is a clear, specific resource description that an agent can match to an install-commands need. It stops short of naming a sibling such as get_software or check_download_link to mark the boundary, so it is clear but not differentiated.

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 infers it should call this when it already has a title slug and needs installation instructions. The schema note that slug is 'as search_software returns it' hints at the search-then-fetch workflow, but the description itself states no when-to-use condition and no alternative tool to prefer for adjacent needs (e.g. verifying a download versus obtaining commands).

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