Skip to main content
Glama

List My Files

list_files
Read-onlyIdempotent

List the files the user uploaded to LuBot.

Returns file id, name, type, upload time and row or chunk count, newest first. Use this when the user asks about their uploaded files, and to find the file_id that analyze_file needs.

Limits: requires sign-in; up to 100 files. Users with no uploads yet see demo files, clearly labeled.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
filesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / $defs / FileMeta / description
      Previous value: -"Public-facing metadata for one file the caller owns.\n\n`file_id` is an opaque string — never a raw DB primary key path or\nfilesystem path — so a compromised token can't be used to probe\ninternal storage layout."New value: +"One file in the user's LuBot account."
    • changedOutput schema / description
      Previous value: -"`list_files` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"files\": [...]}."New value: +"The user's uploaded files (or the labeled sample files)."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "FileMeta": {
      +      "additionalProperties": false,
      +      "description": "Public-facing metadata for one file the caller owns.\n\n`file_id` is an opaque string — never a raw DB primary key path or\nfilesystem path — so a compromised token can't be used to probe\ninternal storage layout.",
      +      "properties": {
      +        "chunk_count": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Chunk Count"
      +        },
      +        "demo_mode": {
      +          "default": false,
      +          "title": "Demo Mode",
      +          "type": "boolean"
      +        },
      +        "file_id": {
      +          "minLength": 1,
      +          "title": "File Id",
      +          "type": "string"
      +        },
      +        "file_type": {
      +          "enum": [
      +            "csv",
      +            "xlsx",
      +            "pdf",
      +            "docx",
      +            "txt",
      +            "image",
      +            "other"
      +          ],
      +          "title": "File Type",
      +          "type": "string"
      +        },
      +        "filename": {
      +          "title": "Filename",
      +          "type": "string"
      +        },
      +        "row_count": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Row Count"
      +        },
      +        "uploaded_at": {
      +          "format": "date-time",
      +          "title": "Uploaded At",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "file_id",
      +        "filename",
      +        "file_type",
      +        "uploaded_at"
      +      ],
      +      "title": "FileMeta",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": false,
      +  "description": "`list_files` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"files\": [...]}.",
      +  "properties": {
      +    "files": {
      +      "items": {
      +        "$ref": "#/$defs/FileMeta"
      +      },
      +      "title": "Files",
      +      "type": "array"
      +    }
      +  },
      +  "title": "FileList",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the auth requirement, the 100-file cap, the newest-first ordering, and the demo-file fallback for new users — behavior an agent cannot infer from structured fields. Nothing contradicts the annotations.

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-loads what is returned before usage guidance and constraints, in four short lines with no filler. Every sentence carries a distinct fact (fields, trigger, limit, edge case).

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?

For a zero-parameter read tool, the definition covers scope, ordering, cap, auth, and the demo-data edge case. An output schema exists, so the field listing is a bonus rather than a required substitute for a return-value spec.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline is 4. The description adds no parameter detail because none is needed.

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?

States a specific verb and resource with scope ('files the user uploaded to LuBot') and enumerates the returned fields. This distinguishes it from the sibling list_portfolio, list_watchlist, and list_websites tools, which cover other resource types.

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 ('when the user asks about their uploaded files') and a concrete secondary purpose (finding the file_id that analyze_file needs), which routes the agent correctly. It does not state when *not* to use it or clarify the boundary against the other list_* siblings, so it falls short of a 5.

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.

Resources