Skip to main content
Glama

Fileion

Look up a file format

lookup_format
Read-onlyIdempotent

What a file extension is (mp3, pdf, heic): its kind, licence, MIME type and typical size, the programs that open it by system, and the Fileion format page.

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": {
      "extension": "<extension>"
    },
    "name": "lookup_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
extensionYesA file extension with or without the dot, e.g. "mp3" or ".heic".

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 declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description goes further by disclosing the actual payload an agent will receive (kind, licence, MIME type, size, per-system programs, format page link), which substitutes for the missing output schema. It stops short of stating failure behavior for unrecognized extensions, which is the one meaningful behavioral gap.

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?

A single compact sentence that front-loads the core answer (what an extension is) followed by the specific fields returned. Nothing is wasted, though the verbless fragment style reads slightly awkwardly and could be tightened without losing content.

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?

This is a simple single-parameter lookup with no output schema, so the description must carry the return-value burden — and it does, listing every category of data returned. Combined with the 100% covered schema and read-only annotations, an agent has nearly everything needed; only unknown-extension handling is unspecified.

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 schema already explains the dot-optional format with examples "mp3" or ".heic". The description's own examples (mp3, pdf, heic) restate that same information rather than adding new constraints, valid ranges, or normalization rules. Baseline 3 applies since the schema does the heavy lifting.

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 the tool returns for a given extension: kind, licence, MIME type, typical size, opening programs by system, and the Fileion format page. That makes the resource and output unmistakable, though it is phrased as a noun fragment rather than a verb+resource statement and does not explicitly distinguish itself from siblings. No sibling confusion is likely given names like lookup_file_hash or check_download_link, but the differentiation is left implicit.

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: the agent supplies an extension and receives descriptive metadata, and the parenthetical examples (mp3, pdf, heic) suggest the expected input domain. There is no explicit when-to-use or when-not-to-use guidance, no mention of what happens with unknown or ambiguous extensions, and no pointer to alternatives such as lookup_file_hash for related lookups. Adequate but with clear gaps.

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