Skip to main content
Glama
Sign In
@memlane/mcp

@memlane/mcp

by danii1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

remove_topic_from_save

Remove a topic assignment from a saved link or note. Unlink a topic to reorganize your saved content.

Instructions

Remove a topic from a saved link or note

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": {
      "itemId": "<itemId>",
      "topicId": "<topicId>"
    },
    "name": "remove_topic_from_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYes
topicIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but fails to mention idempotency, side effects, error conditions, or what happens if the topic is not currently attached. The minimal description leaves significant ambiguity.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it is too sparse and does not earn its place by providing necessary context. It is adequate in length but poor in informativeness.

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

Completeness2/5

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

Given the tool involves modifying data with two parameters and no output schema, the description is insufficient. It does not mention the type of save (link or note), that the operation is specific to that save's topic list, or any return value after removal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the meaning of 'itemId' or 'topicId'. The UUID format is present in the schema but no semantic context is added, leaving the agent to infer critical details.

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 a specific verb 'Remove' and clearly identifies the resource 'topic from a saved link or note', distinguishing it from the sibling tool 'add_topic_to_save'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, or on prerequisites such as that the topic must already be attached to the save. The description lacks context for appropriate use.

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