Skip to main content
Glama

Fileion

Check a download link

check_download_link
Read-onlyIdempotent

Is this web address a source Fileion knows? Answers known or unknown, and for a known one the kind (official, store, mirror, fileion or vendor) and the title with its Fileion page address. For one of Fileion's own download links it names the file that link serves, where that file comes from, and the "N of 5 checks passed" list. The address is only compared with Fileion's records and is never fetched. Unknown means Fileion has no record of the link; it is not a warning.

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": {
      "url": "<url>"
    },
    "name": "check_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA full http(s) address: host and optional port only, no user name or backslash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description goes beyond them by stating the address 'is only compared with Fileion's records and is never fetched' — an important operational guarantee — and by disclosing what the response contains, including the 'N of 5 checks passed' list. It does not contradict any annotation.

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?

The question-form lead sentence front-loads the purpose, and each subsequent sentence adds distinct information (return shape, no-fetch guarantee, interpretation of 'unknown'). The middle sentence about 'kind' and 'title' is slightly run-on, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing return values — and it does, covering the classification, the kind enum, title plus page address, file name and provenance, and the checks-passed summary. For a single-parameter read-only lookup, nothing an agent needs is missing.

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?

With one parameter at 100% schema description coverage, the schema already defines the url format (full http(s), host and optional port, no username or backslash). The description adds no further parameter-level meaning, so the baseline 3 applies.

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?

The description opens with a precise framing ('Is this web address a source Fileion knows?') and then enumerates the exact answer space: known/unknown, the kind (official, store, mirror, fileion, vendor), the title and Fileion page address, plus the deeper per-link detail. The resource (a web address) is clearly distinct from every sibling, which operate on software, files, hashes, or formats.

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 implied rather than stated: an agent can infer this is the tool for validating whether a URL is a recognized source, and the closing line usefully warns that 'unknown' is not an error. However, there is no explicit when-to-use/when-not guidance and no named alternative for adjacent questions (e.g., identifying a file or version behind a link).

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