Transfa
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSFA_API_KEY | No | Optional API key for higher limits. Without it, guest mode applies (10 MB / 24h TTL). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uploadA | Upload a file from the local filesystem and get a signed link. Returns an agent_link (direct download URL for scripts/agents) and a human_link (browser-friendly share page). SHA-256 is always computed and returned for integrity checks. Works without an API key (guest mode, 10 MB limit). Set TRANSFA_API_KEY for larger files and longer TTLs. |
| file_infoA | Get metadata about an upload without downloading it. Returns filename, size, SHA-256, expiry, download count, active status, and whether the file is in a grace period. |
| list_uploadsA | List your recent uploads. Requires TRANSFA_API_KEY or a key saved by |
| delete_uploadA | Delete an upload immediately. Requires ownership (API key must match the uploader). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: uploading, listing, getting file info, and deleting. There is no overlap or ambiguity.
All tools use consistent snake_case with a verb_noun pattern (delete_upload, file_info, list_uploads, upload).
Four tools is well-scoped for a file upload service, covering essential operations without being too few or excessive.
Basic CRUD operations are covered (upload, list, info, delete). Minor gaps like update or TTL management exist but are not critical for the core functionality.