Skip to main content
Glama

Coline

Share a file

share_file
Destructive

Shares a file with people by name or email (they're told), and sets who else may open it: only them, anyone signed in to Coline, or anyone with the link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "fileId": "<fileId>",
      "recipients": "<recipients>",
      "generalAccessMode": "<generalAccessMode>"
    },
    "name": "share_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile or folder id from list_drive_files, search or fetch.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
recipientsYes
publicPasswordNo
generalAccessModeYes
createAuthenticatedLinkNo

Output Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is largely covered. The description does add real value by disclosing the side effect that recipients are notified ("they're told") and by unpacking the meaning of the general access modes. It is silent on password-protected link behavior, whether re-sharing to an existing recipient merges or overwrites access, and whether the notification is email or in-app, which matters for a destructive, externally visible write.

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?

A single tight sentence, front-loaded with the action and followed by the access-scope clause; every phrase carries information. The parenthetical "(they're told)" is slightly informal but earns its place by flagging the notification side effect.

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?

An output schema exists, so return values need not be explained, and the notification behavior plus access-mode semantics are useful additions. Still, for a six-parameter, destructive, external-sharing tool with two undocumented parameters, the description should cover link-password behavior and permission requirements to be fully adequate.

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 coverage is only 33%, so the description must compensate, and it partially does: it explains recipients as names or emails and maps generalAccessMode to the three real-world access scopes. However, two required-ish security parameters, publicPassword and createAuthenticatedLink, receive no explanation anywhere, and the description never links its language back to the restricted/coline_users/anyone enum values explicitly.

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?

Names a specific verb and resource ("Shares a file") and then spells out the two effects: adding recipients by name/email and setting the general access mode. The three access levels are paraphrased in concrete terms ("only them, anyone signed in to Coline, or anyone with the link"), which tells an agent exactly what the operation configures; it stops short of naming a differentiating sibling such as set_file_access.

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

Usage Guidelines2/5

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

The description is entirely about mechanics and offers no when-to-use or when-not-to-use guidance. It never says how this differs from set_file_access, get_file_sharing, or share, nor does it state prerequisites such as needing owner/editor rights on the file.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources