Skip to main content
Glama
Sign In
Fulcra MCP Server

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Files

list_files
Read-only

List files and folders in a Fulcra account or another user's shared paths, and inspect stored versions to discover data for reading or agent coordination.

Instructions

List the files in the user's Fulcra account, or files another user shares.

Files can be used to pass data between agents: one agent writes a file with write_file, others notice the change via get_data_updates and read it with read_file.

Input Schema

NameRequiredDescriptionDefault
pathNoA folder to list (default "/"), or a single file's full path./
fulcra_useridNoList another Fulcra user's shared files. Only shared paths, plus the parent folders leading to them, appear.
include_versionsNoReturn all stored versions of one file, newest first. `path` must then be a single file's full path. Version IDs can be passed to `restore_file`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.18.7
    • removedInput schema / properties / fulcra_userid / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / fulcra_userid / default
      Removed value: -null
    • addedInput schema / properties / fulcra_userid / type
      Added value: +"string"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about shared-user visibility and agent-to-agent file passing, but it does not disclose ordering, pagination, or response shape for a list operation.

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?

The definition is front-loaded with the core purpose and uses two short paragraphs with no repetition. Every sentence adds either scope or useful workflow context.

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 no output schema, the description could say more about what a listing returns, such as file metadata or path structure. Still, for a simple read-only listing tool with fully documented parameters and safety annotations, it provides enough context to call the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents path, fulcra_userid, and include_versions thoroughly, including defaults and constraints. The description does not add syntax or semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific verb and resource: list files in the user's Fulcra account or files shared by another user. It also distinguishes the tool from read_file and write_file by explaining the inter-agent workflow, so an agent can tell what this tool is for without opening the schema.

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?

It gives clear usage context by explaining that files pass data between agents, one writes with write_file, others notice via get_data_updates, and read with read_file. However, it does not explicitly state when to choose list_files over alternatives like read_file, open_file_manager, or get_records, so it lacks explicit exclusions.

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