Skip to main content
Glama

library_scan

Scan a directory for video files and add them to your Unflick library. Use this to import local media so it can be played, clipped, transcribed, and searched.

Instructions

Scan a directory for video files and add them to the library

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": {
      "dir": "<dir>"
    },
    "name": "library_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYesDirectory path to scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral fact that this is a mutating operation (files are added to the library), but omits whether the scan is recursive, how duplicates are handled, whether existing entries are preserved, and whether the call blocks on large directories.

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 efficient sentence with the action and its effect front-loaded and no filler. It is arguably slightly too terse for a tool that mutates persistent state, but nothing is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema the core is covered, but a library-mutating scan realistically needs notes on recursion, duplicate/idempotency behavior, and what happens with an invalid directory before an agent can invoke it confidently.

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?

Only one parameter, and schema coverage is 100% – the schema already states 'Directory path to scan'. The description adds no format details (absolute vs relative, allowed roots) beyond that, so 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?

Names a specific verb and resource ('Scan a directory for video files') plus the side effect ('add them to the library'), which separates it from library_list, library_remove, and library_search. It stops short of naming or contrasting any sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

The only usage signal is implicit: you call it when you want files added. There is no guidance on when to prefer this over other library tools, no prerequisites (valid path, permissions), and no note on whether re-scanning an already-imported directory is safe or expected.

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