Skip to main content
Glama
pslkk

openclaw-syncralis

share_files

Read workspace file contents inline or create a secure, time-limited download link. Always preview file metadata and obtain approval before sharing.

Instructions

Reads or shares workspace files. Three actions are available: 'read' — return file contents inline. For PDFs: (1) If the user specifies a page number, read that range directly using pageStart/pageEnd. (2) If searching for a topic, first read pages 1-10 to find the Table of Contents. If no TOC is found in pages 1-10, extend to pages 1-20, then check the final 10 pages as some PDFs place the index at the back. (3) If the PDF has no TOC, scan in 15-page chunks from the beginning until the topic is located. (4) Always read in chunks of 20 pages or fewer. Never request the full PDF in a single call. (5) If a section appears to continue beyond the chunk boundary, read the next chunk to complete it. (6) For PDFs under 15 pages total, reading the entire document in one call is acceptable. 'preview' — REQUIRED first step before sharing. Returns file metadata (name, size, type, modified) and a short-lived confirmationToken. Present ALL metadata to the user and ask for explicit approval before proceeding. Never skip this step. 'download' — generate a public download link. Requires the confirmationToken returned by a prior 'preview' call for the same file. A link CANNOT be generated without a valid token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesThe name of the file inside the workspace (e.g., invoice.pdf)
actionYesread | preview | download. Always call 'preview' before 'download'.
confirmationTokenNoRequired for action=download. The token returned by the preceding 'preview' call for this exact file.
pageStartNoPDF files only. The first page to return, 1-based (page 1 = first page). Omit only if the PDF is under 15 pages total and you intend to read the whole file.
pageEndNoPDF files only. The last page to return, inclusive and 1-based. Keep the range between pageStart and pageEnd to 20 pages or fewer to avoid context overflow. If the content you need continues beyond pageEnd, make a follow-up call with the next range. Omit only if the PDF is under 15 pages total.
Behavior4/5

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

With no annotations, the description fully carries the behavioral burden. It transparently discloses the multi-step algorithm for PDF reading, the necessity of confirmationToken for download, and that preview returns metadata. However, it does not mention potential side effects or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, especially the PDF reading algorithm (6 bullet-like points). While well-structured and front-loaded with actions, it could be more concise without losing necessary detail.

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?

Given 5 parameters with full schema coverage and no output schema, the description covers all necessary usage context, including workflow constraints and edge cases for PDFs. It is complete for an agent to correctly invoke the tool.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds substantial meaning beyond the schema. For pageStart and pageEnd, it explains chunking and TOC search strategies. For confirmationToken, it clarifies dependency on preview call. The description compensates richly for any missing schema details.

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 clearly states the tool reads or shares workspace files with three distinct actions: read, preview, download. It effectively distinguishes from sibling tools like download_from_url (different source) and save_shared_file (different action).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit workflow: always call 'preview' before 'download', and detailed PDF reading strategies (chunked reading, TOC search, etc.). It tells agents when to use each action and gives step-by-step instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pslkk/openclaw-syncralis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server