Skip to main content
Glama

Coline

Share something

share
Destructive

Shares a thing (a doc, note, sheet, file, folder, task, goal, Kairo answer or chat) with people by email or handle, with a note and what is needed from them. Workspace members get it in Coline. People outside get an email with a link that needs no account; when an assistant or agent shares outside the workspace, it waits for the person's OK in Coline. Use it only when the person asks to share something with someone.

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>",
      "kind": "<kind>",
      "targetId": "<targetId>"
    },
    "name": "share"
  }
}

Input Schema

NameRequiredDescriptionDefault
askNoWhat the sender needs: nothing, feedback, an approval, an answer, a time to meet, or a task done.
kindYesWhat is shared. For any Drive file, "file" works: the file's own type is used.
noteNo
peopleNo
optionsNo
targetIdYes
askDetailNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
linkAccessNo"anyone": anyone with the link can view it.
targetSubIdNoA Kairo answer: the answer's message id.
answerOptionsNoFor an answer: the choices.

Output Schema

NameRequiredDescriptionDefault
heldYesTrue when people outside wait for the person's OK in Coline.
addedYes
draftYes
pageUrlYes
shareIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by describing two distinct delivery paths (workspace members see it in Coline; outsiders get a no-account link by email) and, crucially, that agent-initiated external shares wait for the person's OK. That confirms and explains the destructiveHint=true/openWorldHint=true profile rather than contradicting it. It stops short of saying whether shares are revocable or what the note/ask fields do downstream — the latter is partly covered under ask.

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?

Three sentences, front-loaded with what is shared and with whom, then the internal/external delivery behavior, then the usage restriction. Dense but every clause carries information; only the parenthetical kind list is slightly long.

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?

For an 11-parameter mutation tool with nested objects, the description covers the main flow and the approval behavior well, and an output schema exists so return values need not be described. But the options object (chatFrom, outputIds, askEnabled, mustSignIn, showHowMade, briefEnabled) and access/linkAccess semantics are undocumented, leaving real gaps for correct invocation.

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?

With 55% schema coverage, the description compensates for some gaps: it explains that recipients are identified "by email or handle," that a note accompanies the share, and that "what is needed from them" maps to the ask concept. However, it adds nothing about access levels (view/comment/edit), linkAccess, or any of the five booleans in options, leaving several parameters understood only from terse 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 ("Shares") and enumerates the resources it covers ("a doc, note, sheet, file, folder, task, goal, Kairo answer or chat"), plus the recipient channel (email or handle). It does not differentiate itself from the sibling tools share_file and share_calendar, which an agent must resolve on its own.

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?

"Use it only when the person asks to share something with someone" is an explicit gating condition that rules out proactive sharing. It also explains the internal-vs-external recipient split, but gives no guidance on how to choose among sharing siblings or how access levels should be picked.

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