Skip to main content
Glama

propose_share

Read-only

Prepare sharing a note or folder with a person. Nothing is shared: you get a link for the user that opens Cobrain's «Who has access» window filled in with the email and permission, and the user confirms there with one click. Use only when the user asked to share; who_sees lists the emails of people already in the brain.

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": {
      "path": "<path>",
      "email": "<email>"
    },
    "name": "propose_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoDefault read
pathYesNote or folder
emailYes
workspaceNoUsually omit; else brain id (as in search hits), 'mine', or owner name/email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description goes further and explains the actual mechanism: "Nothing is shared," the agent gets a link, and the human confirms in Cobrain's «Who has access» window. That handoff detail is exactly the context an agent needs to avoid misrepresenting the call as a completed share.

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 the core "prepare, not share" distinction and the confirmation flow. The trailing who_sees sentence is slightly bolted on but is short and routing-relevant, so little is wasted.

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?

There is no output schema, and the description usefully discloses what the caller receives (a pre-filled link). For a four-parameter, non-destructive preparation tool with annotations covering safety, the only real gap is the meaning of mode read vs write, which is left to the enum's own description.

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 75% and the schema already documents mode (default read), path, and workspace, so the structured fields carry most of the weight. The description adds no meaning for path, email, or mode; its only parameter-adjacent sentence is about who_sees rather than about what to pass here, so the baseline 3 applies.

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?

States a specific verb+resource: "Prepare sharing a note or folder with a person." It immediately clarifies the tool does not share but prepares a share, which separates it from a real mutation and from the sibling who_sees, which it names explicitly.

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 only when the user asked to share" gives an explicit gating condition rather than vague context. It also points at who_sees for the related question of existing access, but does not spell out an explicit when-not or a full alternative-selection rule.

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