Skip to main content
Glama

recent_files

List played video files newest first, showing play counts and timestamps and including files opened directly. Use it to resume viewing or review your watch history.

Instructions

Recently played files, newest first, with how many times each was played and when. Covers files opened directly, not just ones scanned into the library.

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": "recent_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (1-200, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose ordering, the two derived fields returned per file, and an important coverage nuance (directly opened vs. library-scanned). It says nothing about read-only safety, whether history persists across sessions, or how the list is bounded apart from the schema's limit.

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 zero filler, and the core output shape (newest first, play count, timestamp) is front-loaded before the scope caveat. Every clause carries information.

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 tool with no output schema, the description covers what comes back and in what order, which is what an agent needs to call it. Minor gaps remain around persistence of history and whether results are capped or paginated beyond limit.

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?

The single parameter is fully documented in the schema with its range (1-200) and default (20), so the schema does the heavy lifting. The description adds no meaning about what limit counts against or whether truncation is signaled, leaving this at baseline for 100% coverage.

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 names the resource (recently played files) and characterizes the payload precisely: newest first, with play counts and last-played timestamps. That distinguishes it from a plain library listing, though it never names the sibling recent_clear or otherwise contrasts itself with adjacent tools.

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 clause 'Covers files opened directly, not just ones scanned into the library' is a useful scope boundary that implies when this is the right source of history. There is no explicit when-to-use, no named alternative, and no mention of when the history should be cleared or refreshed instead.

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