Skip to main content
Glama

overleaf_list_files

Lists the complete folder and file tree inside an Overleaf project using a project ID, URL, or exact title.

Instructions

List the complete folder and file tree inside an Overleaf project.

Args: project: Overleaf 24-char project ID, full project URL, or exact project title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "overleaf_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/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. It signals completeness ("complete folder and file tree") and implies a read-only operation, but says nothing about authentication prerequisites, whether hidden or binary files appear, depth limits, or truncation on large projects.

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?

The purpose sentence is front-loaded and the parameter note is compact; nothing is wasted. The "Args:" docstring block is slightly redundant formatting but justified given the empty schema description.

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

Completeness3/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, and the single parameter is well covered. However, for a tool with zero annotations the description should say more about read-only semantics and auth expectations before an agent calls it in a project it hasn't confirmed access to.

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 0% — the schema only declares a bare string — so the description must compensate, and it does: it specifies that `project` accepts a 24-char project ID, a full project URL, or an exact project title. That is meaningful resolution guidance well beyond the schema, though it doesn't discuss ambiguity when a title matches multiple projects.

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?

The description states a specific verb and resource: "List the complete folder and file tree inside an Overleaf project." That scope (tree within a single project) naturally separates it from overleaf_list_projects, but the description never names or contrasts any sibling, so it stops short of explicit differentiation.

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?

Usage is only implied by the word "List" and the project-scoped phrasing; an agent can infer this is the discovery step before overleaf_read_file or overleaf_write_file. There is no explicit when-to-use, when-not-to-use, or mention of alternatives.

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