Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Share one of my files by link

connections_storage_share_file
Destructive

A link anyone can open, no account needed, to one of the member's files: how to send a file to someone outside Connections. fileName must be the file's listed name or no link is made. Works for days (default 7, max 30); the member can turn it off in Files. Add password (4-128 characters) and whoever opens the link must type it first; only a hash is kept, and it is never shown again. Every download through a link is recorded: share_downloads shows who and when.

Input Schema

NameRequiredDescriptionDefault
daysNoDefault 7, maximum 30.
fileIdYesFrom list_files, search or save_file.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
dry_runNoPreview only.
projectNoWorkspace to run this call in (id or name).
fileNameYesExactly as listed.
passwordNoOptional. 4-128 characters the person opening the link must enter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / password
      Added value: +{
+  "description": "Optional. 4-128 characters the person opening the link must enter.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only; nothing is written."New value: +"Preview only."
  3. Changed3 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"How many days the link works (default 7, maximum 30)."New value: +"Default 7, maximum 30."
    • changedInput schema / properties / fileId / description
      Previous value: -"The file's id, from list_files, search or save_file."New value: +"From list_files, search or save_file."
    • changedInput schema / properties / fileName / description
      Previous value: -"The file's name exactly as list_files, get_file or save_file showed it."New value: +"Exactly as listed."
  4. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is largely pre-supplied. The description adds real value on top: the link is publicly openable without an account, an exact fileName match is required or no link is made, expiry is capped at 30 days, passwords are stored only as a hash and never shown again, and downloads are recorded. It never states that the tool returns the link itself, which is the one behavioral fact an agent most needs.

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

Conciseness4/5

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

Dense but front-loaded, with the public-link nature established first and constraints following; every clause carries information. The opening sentence is awkwardly spliced with a colon and the 'member can turn it off in Files' note is tangential, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should describe what the call yields, yet it never mentions that a shareable URL is returned or what happens if the call fails on a fileName mismatch. It is otherwise thorough for a 7-parameter mutation, covering lifetime, protection and audit consequences.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3, but the description adds meaning beyond the schema for two parameters: fileName must match the listed name exactly or the call silently produces no link, and the password is one-way hashed and unrecoverable after creation. The days and password bounds merely restate schema text.

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 and resource — creating a public no-account link to one of the member's stored files — and the opening clause 'how to send a file to someone outside Connections' frames the outcome. It distinguishes itself implicitly from list_files (source of fileId) and share_downloads (audit trail), though it does not name a sibling sharing alternative.

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?

Gives a clear triggering condition ('send a file to someone outside Connections') and routes the agent to share_downloads for the audit side of the workflow. It lacks an explicit when-not clause or a named alternative for internal-only sharing, so it stops just short of full routing guidance.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources