Skip to main content
Glama
nuwainfo

ffl-mcp

Official
by nuwainfo

fflShareText

Shares text content through a secure link with optional encryption, authentication, download limits, and inactivity timeout. Returns a clickable link and optionally a QR code for terminal display.

Instructions

Share text content using ffl. Returns a sessionId and link. If qrInTerminal is True, also returns a QR code as ASCII art for terminal display.

IMPORTANT: Always present the returned link so the user can click it to open in a browser. Do not display it as a plain unformatted URL — in some interfaces (such as Claude Dispatch) plain URLs are not auto-linked and will not be clickable.

Args: text: Text content to share name: Download filename shown to recipient (default: shared.txt) e2ee: Enable end-to-end encryption (default: False) authUser: HTTP Basic Auth username to protect the link authPassword: HTTP Basic Auth password to protect the link maxDownloads: Stop serving after N downloads (default: 1) timeoutSeconds: Stop serving after N seconds of inactivity (default: 1800) waitLinkSeconds: Seconds to wait for link generation hookUrl: Custom webhook URL for events proxy: Proxy server URL (e.g. socks5://127.0.0.1:9050) qrInTerminal: Return ASCII QR code art for terminal display recipientAuth: Recipient authentication mode — pickup (6-digit code), pubkey (RSA challenge), pubkey+pickup (both), email (OTP) pickupCode: Specific pickup code to use (default: auto-generated) recipientPublicKey: Path to recipient .fflpub public key file for pubkey auth recipientEmail: Recipient email(s) for OTP auth, comma-separated alias: Custom link alias instead of random UID (requires Standard+ account) receipt: Send email notification when recipient downloads (pass email address, or empty string for account email) receiptConfirm: Require recipient to confirm before download starts; pass confirmation message or empty string for default forceRelay: Disable direct WebRTC; route all traffic through tunnel port: Local HTTP server port (default: auto-detect) invite: Open invite page in browser with the sharing link enableReporting: Enable ffl error reporting for diagnostics (disabled by default)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
nameNoshared.txt
e2eeNo
authUserNo
authPasswordNo
maxDownloadsNo
timeoutSecondsNo
waitLinkSecondsNo
hookUrlNo
proxyNo
qrInTerminalNo
recipientAuthNo
pickupCodeNo
recipientPublicKeyNo
recipientEmailNo
aliasNo
receiptNo
receiptConfirmNo
forceRelayNo
portNo
inviteNo
enableReportingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the primary function, return values, and parameter effects, but does not address error handling, side effects, or limitations. The description is informative but leaves some behavioral aspects implicit.

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 structured with an introductory sentence, an important usage note, and a bulleted parameter list. While verbose due to 22 parameters, the structure is logical and front-loaded with key information. Some redundancy could be trimmed, but it is functional.

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?

Given the tool's complexity (22 parameters, 1 required), the description covers the core functionality, return values (sessionId, link, optional QR), and parameter details. It lacks explicit error handling or edge case guidance, but for selecting and invoking the tool, it provides sufficient context.

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?

Schema coverage is 0%, meaning no parameter descriptions in the JSON Schema. However, the tool description provides a comprehensive 'Args' section detailing every parameter's purpose, default values, and constraints (e.g., types, defaults, special conditions). This fully compensates for the schema gap.

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 'Share text content using ffl' and mentions returning a sessionId and link. This is a specific verb+resource, and the shared context with sibling tools (e.g., fflShareFile, fflShareBase64) differentiates it effectively.

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?

The description provides important usage guidance, such as how to present the link to users and the optional QR code behavior. However, it does not explicitly compare to sibling tools or state when not to use this tool, though the context implies text sharing.

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/nuwainfo/ffl-mcp'

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