Skip to main content
Glama

graph_list_recent_files

List recently worked-on files across OneDrive to review recent activity and page through larger result sets.

Instructions

List what the user worked on recently across their OneDrive.

Args: top: Maximum number of items to return (default 25, maximum 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does well on paging mechanics (50-item cap per call, next_link overriding other paging arguments, include_next_link controlling result wrapping), but it never defines what 'recently' means (ordering, time window) or notes any permission/auth requirements.

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?

Front-loaded one-line purpose followed by a compact Args block; every parameter line adds information and there is no filler text.

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 paged list tool with no output schema and no annotations, the description covers the important mechanics: paging strategy, the returned shape under include_next_link, and parameter interaction. The main omission is a definition of 'recent' ordering or time window.

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 description coverage is 0%, so the description must compensate, and it documents all four parameters with defaults and behavior. It even adds constraints absent from the schema, notably the 'maximum 50' cap on top and the fact that next_link overrides the other paging arguments — a meaningful semantic that the schema cannot express.

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 specific verb and resource ('List what the user worked on recently across their OneDrive'), which is clear enough to separate it from a generic listing of files. It does not name a sibling alternative such as graph_list_files, so the differentiation is implied by 'recently' rather than made explicit.

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 recency framing implies when this tool is appropriate versus a full file listing, but there is no explicit 'use this when / use X instead' guidance or statement of prerequisites. Guidance is inferable rather than stated.

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