Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

Forget a shared memory

memory_forget
DestructiveIdempotent

Remove one fact from the user's RelayLink shared memory, by the id whoami or memory_search printed beside it. Call this when they ask you to forget something, alongside forgetting it in your own memory. It deletes the RelayLink copy and nothing else: say that you have removed it from RelayLink rather than claiming it is gone everywhere, because this cannot reach what another assistant holds. Deleting is permanent and there is no undo. It works even when shared memory is switched off for the account.

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": "memory_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id from whoami's memory block or a memory_search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains that deletion is permanent with no undo, that it only removes the RelayLink copy, and that it cannot affect what another assistant holds. It also notes the operation works even when shared memory is switched off for the account, which is useful operational context.

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?

The description is front-loaded with the core action and id source, then follows with necessary cautions about permanence and scope. Every sentence carries useful information without redundancy.

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?

For a destructive single-parameter deletion tool with annotations covering destructiveness and idempotency, the description provides the key behavioral context: what gets deleted, what does not, permanence, and availability when shared memory is off. No output schema exists, so return-value explanation is not needed.

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%, so the id parameter and its source are already documented in the schema. The description reinforces that the id comes from whoami or memory_search, but it adds no new syntax or format detail beyond the 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?

The description states a specific verb and resource: remove one fact from the user's RelayLink shared memory by id. It distinguishes this from memory_search and whoami by explaining that those tools provide the id, and from memory_add by making clear this is a deletion operation.

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?

It gives a clear trigger: call this when the user asks you to forget something, alongside forgetting it in your own memory. It also explains the scope limitation, but it does not explicitly name an alternative tool or exclusion beyond the note that other assistants cannot be reached.

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

All RelayLink toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources