Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read File

read_file
Read-only

Reads a file from your Fulcra account or one shared with you, returning contents or a temporary download link. Spreadsheets return as CSV, one section per sheet.

Instructions

Read a file from the user's Fulcra account, or one another user shares. Spreadsheets (.xlsx) come back as CSV, one section per sheet.

Input Schema

NameRequiredDescriptionDefault
pathYesThe full path of the file to read.
as_linkNoInstead of the contents, return a link the user opens to download the file, e.g. a spreadsheet. It works for 10 minutes.
max_bytesNoTruncate text content beyond this many bytes (default 100000). Pass a larger value only when the full content is truly needed; large files consume a lot of context.
fulcra_useridNoRead a file of another Fulcra user (if shared).
include_binaryNoReturn other binary files base64-encoded (default false); this uses a lot of context.

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. Changed2 schema fields changedv1.2.4
    • addedInput schema / properties / as_link
      Added value: +{
+  "default": false,
+  "description": "Instead of the contents, return a link the user opens to\ndownload the file, e.g. a spreadsheet. It works for 10 minutes.",
+  "type": "boolean"
+}
    • changedInput schema / properties / include_binary / description
      Previous value: -"Return non-UTF-8 files base64-encoded (default false).\nOtherwise binary files are refused with their size."New value: +"Return other binary files base64-encoded (default\nfalse); this uses a lot of context."
  3. Addedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely non-obvious behavior beyond that: spreadsheets are returned as CSV with one section per sheet, and the cross-user sharing scope. It omits the truncation-by-default and base64 behaviors, but those are documented in the schema fields.

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?

Two sentences, both front-loaded with the primary action first and the format caveat second. Nothing is wasted and there is no restating of the title.

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 read-only tool with full schema coverage and annotations, the description covers source scope and the one surprising return-format behavior. A brief note on default truncation or that binary content is opt-in would make it complete, but the schema already carries those details.

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 all five parameters (path, as_link, max_bytes, fulcra_userid, include_binary) are already fully explained in the schema. The description's clause about another user's shared files loosely corresponds to fulcra_userid but adds no syntax or format detail. Baseline 3 applies.

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+resource ('Read a file from the user's Fulcra account, or one another user shares'), which is enough to separate it from list_files/write_file/delete_file by operation. It stops short of explicitly naming those siblings, but the resource scope (shared vs. own files) is stated precisely.

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 implied by the verb — read a file when you need its contents — but there is no explicit when-to-use guidance (e.g. when to call read_file vs. list_files to discover a path, or when to use open_file_manager). No exclusions or alternatives are named.

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