Skip to main content
Glama

Recent Files

recent_files
Read-onlyIdempotent

Identify files modified within a specified number of days in a folder using Spotlight search.

Instructions

Find recently modified files in a folder using Spotlight.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFolder to search (default: home)~
daysNoModified within N days (default: 7)
limitNoMax results (default: 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
filesYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description doesn't need to cover those. It adds 'using Spotlight' which implies reliance on the Spotlight index, offering mild behavioral context beyond annotations.

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 one sentence of 8 words, extremely concise and front-loaded with the key action and resource.

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?

With a present output schema and complete annotations, the description is sufficient for a simple file-finding tool. However, it lacks detail on what information is returned (e.g., file paths, dates) or potential limitations, but overall acceptable.

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?

All three parameters (folder, days, limit) are fully described in the input schema (100% coverage). The description does not add any additional semantic information about parameters beyond what the schema provides.

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

Purpose5/5

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

The description uses 'Find recently modified files' which clearly states the verb and resource, and 'using Spotlight' adds specificity. It distinguishes from sibling tools like search_files and list_directory by focusing on recent files via Spotlight.

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 description does not provide guidance on when to use this tool versus alternatives. It mentions Spotlight but no comparison to search_files or list_directory, nor any conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heznpc/AirMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server