Skip to main content
Glama

List recent files

list_files
Read-onlyIdempotent

Files on FynePDF from the last 24 hours, newest first: what the person dropped in the upload box, other uploads and imports, and results. Use it to find the file_id of a file the person says they uploaded, by its name.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryNoPart of a file name.

Output Schema

NameRequiredDescriptionDefault
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / files / items / properties / bytes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / bytes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior: a hard 24-hour recency window, newest-first ordering, and the fact that results, imports, and upload-box drops are all included. It does not explain pagination or how truncation interacts with limit, which keeps it below 5.

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?

Two sentences, with the scope (24 hours, newest first) and the enumeration of included file types front-loaded before the use case. The colon-list of sources ('upload box, other uploads and imports, and results') is slightly wordy, but each clause carries information an agent needs.

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 an output schema, full schema description coverage, and rich annotations, the description only needs to convey scope and intent, and it does. The main remaining gap is disambiguation from list_library_files and get_file in a crowded 26-tool namespace. Nothing about calling it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented (limit with default 10, query as part of a file name). The description adds meaning beyond that: 'newest first' implies limit returns the most recent N, and 'by its name' confirms query matches on file name. This is incremental but genuine value over the schema baseline of 3.

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?

States a concrete verb and resource with scope: files from the last 24 hours, newest first, covering uploads, imports, and results. An agent immediately knows it is a recent-files listing. It stops short of 5 because it never names the closely related siblings (list_library_files, get_file), so the boundary is left implicit.

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

Usage Guidelines4/5

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

Gives an explicit trigger: use it to resolve the file_id of a file the person says they uploaded, looked up by name. That is a real when-to-use statement rather than an implied one. It offers no when-not or named alternative, so an agent cannot tell from the text alone when to prefer list_library_files or search_docs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.