Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

List file types

resolve_file_type
Read-only

Retrieves supported file types and file type groups, helping you find the exact Aether file-type name before running a file-type search.

Instructions

Get Aether's supported file types and file type groups.

When to use: Before searching by file type, to get its exact Aether name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_file_type"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the substantive detail that the return covers both file types and file type groups. That helps the agent anticipate a taxonomy-shaped response despite there being no output schema. It does not say whether the list is static or how large it is, so a small gap remains.

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 sentences, both earning their place: the first says what is returned, the second says when to call it. The purpose is front-loaded and the guidance follows immediately with no filler.

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 zero-argument reference lookup with no output schema, the description covers what it returns and why an agent would call it. The only missing piece is the response shape, such as whether names come back as a flat string list or grouped objects, which matters slightly more given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. Nothing in the description misrepresents the input contract.

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 and resource: retrieving Aether's supported file types and file type groups. This makes clear it is a static reference listing rather than a per-file type resolver, which is the key distinction from the similarly named resolve_file_type title. It stops short of naming any sibling for contrast, so it lands at 4 rather than 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?

An explicit 'When to use' clause is given: call this before searching by file type to obtain the exact Aether name. That is a real trigger condition tied to a downstream workflow, not just a restatement of purpose. No when-not guidance or named alternative is offered, so it is clear context without exclusions.

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