Skip to main content
Glama

List file information

list_files
Read-onlyIdempotent

List accessible file metadata within a project or task; provide projectId or taskId. This tool does not download file content or expose storage credentials.

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
afterNoPagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
limitNoMaximum number of items to return, from 1 to 100. Defaults to 50.
orderNoResult ordering. Defaults to most recently updated first. Keep the same order while paging.UPDATED_DESC
taskIdNoExisting accessible task ID returned by list_tasks or search.
projectIdNoExisting accessible project ID returned by list_projects.

Output Schema

NameRequiredDescriptionDefault
itemsYesAccessible records on this page.
nextCursorYesPass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by stating the negative scope — no file content is returned and no storage credentials are exposed — which prevents an agent from misusing this as a download tool. It stops short of describing result shape or pagination limits, but pagination is documented in the schema.

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?

A single compact sentence pair with zero filler: the capability and its scope come first, followed by the negative boundary. Every clause carries information an agent needs, and nothing is repeated from the schema or annotations.

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 small five-parameter schema, full schema descriptions, an output schema and rich annotations, the description only needs to establish intent and boundaries, which it does. The one remaining gap is that it never clarifies what happens when both projectId and taskId are omitted, despite neither being required.

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 100%, so the baseline is 3, but the description adds a constraint the schema does not encode: at least one of projectId or taskId should be supplied even though neither is formally required. That is meaningful guidance for constructing a valid call, above what the schema states.

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 names a specific verb and resource ('List accessible file metadata') and scopes it to 'within a project or task', which is concrete enough for an agent to act on. It also distinguishes itself from content-retrieval tools by stating it does not download file content, though it does not name the sibling (e.g. list_docs, get_doc) that would be used instead.

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?

It gives a calling condition ('provide projectId or taskId'), which is real usage guidance. However, it offers no when-not guidance nor any explicit alternative for retrieving file content or searching across projects, so the agent must infer the routing decision from sibling names alone.

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.