Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Look up a local file

lookup_file
Read-only

Hashes a local file with SHA-256 and returns its hash plus Aether reputation without uploading the file, helping you check whether Aether recognizes a provided file path.

Instructions

Hash a local file (SHA-256) and return the hash and Aether's reputation for it. The file is never uploaded.

When to use: When the user shares a file path in their own message and wants to know if Aether knows it.

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": {
      "path": "<path>"
    },
    "name": "lookup_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull local path of the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already signals a safe read, so the description's key contribution is the explicit 'the file is never uploaded' privacy guarantee and the statement that it computes SHA-256 and returns both the hash and a reputation result. That is meaningful behavior an agent cannot infer from the annotation. It stops short of disclosing edge cases such as unknown hashes, unreadable files, or size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core behavior front-loaded and a clearly labeled 'When to use' clause. Every sentence carries information: what it does, what it returns, what it does not do with the file, and the trigger condition. Nothing is redundant.

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 one-parameter, read-only tool the description covers the essentials: input semantics, privacy behavior, and what comes back (hash plus reputation). With no output schema present, the return-value sentence is doing necessary work. Minor gaps remain around failure or unknown-file behavior, but nothing critical for correct invocation 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?

There is a single parameter, 'path', and the schema already documents it as the full local path with 100% coverage. The description confirms the file is local and clarifies that it is hashed rather than uploaded, but adds no format, permission, or size constraints beyond the schema. With the schema doing the heavy lifting, the baseline of 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 gives a specific verb and resource: it hashes a local file with SHA-256 and returns both the hash and Aether's reputation verdict. That is concrete enough to distinguish it from siblings such as lookup_hash (which presumably takes an existing hash) or scan_file. It does not explicitly name or contrast with those siblings, so it falls short of a 5.

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?

The 'When to use' line gives a clear trigger: the user shares a file path in their own message and asks whether Aether knows the file. That is real, actionable context rather than implied usage. However, it offers no when-not-to-use guidance or pointer to alternatives like scan_file for deeper analysis or resolve_file_type for type identification.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.