Skip to main content
Glama

file_info

Retrieve duration, resolution, and codec details from a media file without affecting ongoing playback.

Instructions

Get media file metadata (duration, resolution, codecs) without affecting current playback

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": {
      "file": "<file>"
    },
    "name": "file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly discloses that this is a read-only metadata operation and that it does not affect current playback, which is important behavioral context. It does not cover error cases such as missing files or unsupported formats, so it is not fully complete.

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?

The description is a single, front-loaded sentence with no wasted wording. It states the action, the metadata returned, and the non-disruptive behavior efficiently.

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 simple one-parameter read tool with full schema coverage, the description supplies the essential purpose, examples of returned metadata, and the key non-side-effect behavior. No output schema exists, but the description sufficiently indicates the kind of information returned.

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 one parameter ('file') and schema description coverage is 100%, so the schema already documents its meaning as a media file path. The description adds no additional parameter-level meaning beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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 uses a specific verb and resource ('Get media file metadata') and names concrete metadata fields (duration, resolution, codecs). It implies differentiation from playback-related siblings by stating the operation does not affect current playback, though it does not name an alternative tool explicitly.

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?

The phrase 'without affecting current playback' gives clear implied usage: inspect metadata while leaving playback state untouched. However, there is no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the many media siblings.

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

Deploy Server

Other Tools