Skip to main content
Glama
Sign In
folder-index

folder-index

by git-raka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recent_files

Find recently modified or downloaded files in an indexed folder, filter by extension, and set a result limit to locate new or changed files.

Instructions

Most recently modified/downloaded files.

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
extNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.2/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 behavioral burden and discloses almost nothing: no ordering guarantee, no statement that 'modified' and 'downloaded' are combined or how, and no note about the default limit of 15 or what happens when nothing recent exists. It only implies a read-style listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with zero filler and the recency qualifier is front-loaded, but it is under-specified rather than concise — the terseness removes necessary information instead of trimming redundancy.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but with no annotations and undocumented parameters the definition leaves the agent without the basics: what 'recent' means, what ext does, and how limit affects output.

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

Parameters1/5

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

Schema description coverage is 0%: 'ext' and 'limit' have bare titles and defaults with no explanation, and the description never mentions either. The agent cannot learn from the description that ext filters by file extension or that limit caps result count, so nothing compensates for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Most recently modified/downloaded files' identifies the resource and the recency ordering, so an agent can infer this lists files rather than reading or searching them. However, there is no verb and no explicit differentiation from siblings like find_files or search_files, so purpose is only implied.

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?

No guidance on when to use this instead of find_files or search_files, and no mention of what 'recent' means (time window, index freshness). The agent is left to guess from the name alone.

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