Skip to main content
Glama

Revoke a memory share link

revoke_memory_share
DestructiveIdempotent

Use this when the user asks to revoke, cancel or turn off a share link. Stops all future imports from that link. Copies that were already imported stay in the other vaults. Takes the share id from list_memory_shares.

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": {
      "id": "<id>"
    },
    "name": "revoke_memory_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShare id, starts with shr_.

Output Schema

NameRequiredDescriptionDefault
idNo
revokedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: future imports are blocked while already-imported copies persist in other vaults, which is exactly the consequence an agent needs before confirming a destructive action.

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?

Four short sentences, front-loaded with the trigger condition, then consequences, then parameter sourcing. Every sentence carries distinct information with no repetition of the title or schema.

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?

An output schema exists, so return values need not be explained. For a single-parameter destructive tool, the description covers trigger, effect on future imports, effect on past imports, and where to get the id — nothing an agent needs is missing.

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% and the schema documents the shr_ prefix and length bounds, so the baseline is 3. The description adds provenance beyond the schema by telling the agent to source the id from list_memory_shares, which is useful operational guidance not encoded anywhere in the input schema.

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 set (revoke/cancel/turn off) against a specific resource (a share link), and the title plus description make the effect unambiguous. An agent can distinguish this from create_memory_share or import_memory_share without opening any schema.

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 an explicit trigger condition ('when the user asks to revoke, cancel or turn off a share link') and routes the agent to list_memory_shares to obtain the id. It stops short of stating when not to use it or what to do if the share is already revoked, but the usage context is clear.

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