Skip to main content
Glama

Recent files

recent_files
Read-only

List recently modified files newest first and session edits to identify changes when starting or resuming work or after build, format, or git steps.

Instructions

List recently modified files, newest first, plus session_edits (files you wrote in this session). Use when: you start or resume a task, or finished a build, format or git step and want to see what changed. Feed the top paths into read_batch. Avoid when: you need the full tree (list_files) or a content search (search). Output: entries[] {relative_path, size_bytes, modified_ago_seconds}, session_edits, truncated.

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
depthNoDirectory recursion cap (default 2, max 6).
limitNoMax entries (default 20, max 100).
relative_pathNoWorkspace-relative ('.' = root); absolute/.. outside it rejected.
include_ignoredNotrue also lists ignored folders (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.5.0
    • removedInput schema / properties / include_ignored / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "maximum": 1,
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / include_ignored / description
      Previous value: -"1 also lists ignored folders (default 0)."New value: +"true also lists ignored folders (default false)."
    • removedInput schema / properties / include_ignored / maximum
      Removed value: -1
    • removedInput schema / properties / include_ignored / minimum
      Removed value: -0
    • changedInput schema / properties / include_ignored / type
      Previous value: -"integer"New value: +"boolean"
  2. Addedv4.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description still adds real behavioral detail: newest-first ordering, the fact that session_edits are returned alongside filesystem results, and that results can be truncated. It stops short of explaining how truncated interacts with limit or how session_edits counts against the cap, which keeps it from a 5.

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?

Four tight lines with the purpose front-loaded, then labeled Use when / Avoid when / Output sections and a sibling hand-off. Every clause carries information; there is no filler or restatement of the title.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the returned fields (relative_path, size_bytes, modified_ago_seconds) plus session_edits and truncated. Combined with named alternatives and clear invocation triggers, an agent has everything needed for a zero-required-parameter read tool.

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?

Schema description coverage is 100%, with depth, limit, relative_path and include_ignored each documented including defaults and bounds, so the schema does the heavy lifting. The description adds no parameter-level meaning such as how depth interacts with truncation or whether ignored folders appear in session_edits, so the baseline 3 applies.

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?

"List recently modified files, newest first, plus session_edits" gives a specific verb (List), resource (recently modified files), explicit ordering, and a distinguishing extra payload (session_edits) that no sibling offers. It is immediately separable from list_files and search, which are named in the same breath.

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

Usage Guidelines5/5

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

Contains explicit "Use when" triggers (task start/resume, after build/format/git steps) and explicit "Avoid when" exclusions that route to list_files for a full tree and search for content search. It also prescribes the natural next step, feeding top paths into read_batch, so the agent knows both selection and follow-up.

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