Skip to main content
Glama
Sign In
Cachly — AI Cognitive Brain

Cachly — AI Cognitive Brain

by cachly-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

brain_unshare

Revoke and permanently delete a public Brain share using its share ID, making the share URL invalid and blocking new imports.

Instructions

Revoke and permanently delete a public Brain share by its share ID. After calling this, the share URL becomes invalid and no one can import it. Note: users who already imported the Brain keep their local copy. Example: brain_unshare(instance_id="...", share_id="abc123")

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": {
      "instance_id": "<instance_id>",
      "share_id": "<share_id>"
    },
    "name": "brain_unshare"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYesShare ID to revoke (from brain_share or brain_share_list).
instance_idYesUUID of the Brain instance that owns the share.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.47

TDQS

A4.3/5.0
Behavior4/5

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

The description clearly discloses that the action is irreversible (share URL becomes invalid) and warns that users with imported copies keep them locally. With no annotations, this provides important behavioral context beyond the schema.

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

Conciseness5/5

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

Three sentences—each adds unique value: action description, consequence, and example. No redundancy or filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two required parameters and no output schema, the description fully explains the tool's effect, side effects, and includes an example, making it complete.

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 100% and both parameters have clear descriptions in the schema. The description adds a usage example but does not add semantics beyond what the schema already provides, warranting a baseline 3.

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?

The description uses specific verbs ('Revoke and permanently delete') and resources ('public Brain share by its share ID'), clearly distinguishing it from siblings like brain_share and brain_share_list.

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?

The description implies usage context by stating the share URL becomes invalid and no one can import it. However, no explicit alternative is given when the user wants to temporarily disable a share.

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

Deploy Server

Other Tools