Skip to main content
Glama

Fileion

Look up a file hash

lookup_file_hash
Read-onlyIdempotent

Is this file one Fileion has scanned? Give the SHA-256 (or SHA-1 / MD5) of a download. If found: the title, version, file, "N of 5 checks passed", the official source host and the Fileion page address. Not found means Fileion has no record of the file; 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": {
      "hash": "<hash>"
    },
    "name": "lookup_file_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesThe file's SHA-256 (64 hex characters), SHA-1 (40) or MD5 (32).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), but the description adds substantive context the annotations cannot: the exact return payload (title, version, file, 'N of 5 checks passed', official source host, Fileion page address) and, critically, that a miss is an absence of record rather than a red flag. That negative-result semantics is exactly the kind of disclosure that prevents agent misreporting.

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 opens the description, followed immediately by the action and then the result contract, so it is well front-loaded and short. The return-field sentence is slightly awkward as a fragment ('the title, version, file, "N of 5 checks passed"'), which costs a point but does not impede comprehension.

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?

With no output schema, the description carries the return-value burden and does so explicitly, listing each returned field plus the meaning of an empty result. For a one-parameter read-only lookup that is sufficient for an agent to call it and interpret the answer correctly.

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 the single parameter already documents accepted formats and lengths, so the description's mention of SHA-256/SHA-1/MD5 merely echoes the schema. Baseline 3 is correct: no added syntax, normalization, or case-sensitivity guidance beyond the structured field.

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 states a specific verb (look up / check) and resource (a file hash against Fileion's scan records) via the front-loaded question 'Is this file one Fileion has scanned?'. It is clearly distinguishable from search- or list-oriented siblings, though it never names an alternative tool to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context ('Give the SHA-256 (or SHA-1 / MD5) of a download') and a valuable interpretation rule for the negative case: 'Not found means Fileion has no record of the file; it is not a warning.' It stops short of naming when to use this versus a related tool such as a link checker, so no exclusions are stated.

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