Skip to main content
Glama
Sign In
@memlane/mcp

@memlane/mcp

by danii1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_save

Retrieve a specific saved link or note using its identifier, with an option to include the full markdown content.

Instructions

Get a saved link or note by id, optionally including full markdown content

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

Input Schema

NameRequiredDescriptionDefault
idYes
includeContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It indicates that the tool reads a single item and optionally includes full content, but omits details on side effects, permissions, rate limits, or return format, which are critical for safe invocation.

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 a single sentence with no unnecessary words. It is front-loaded and efficiently conveys the core action and key option.

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?

For a simple retrieval tool with no output schema, the description should at least mention the return structure or error cases. It only covers the input, leaving the agent uninformed about what to expect, which is incomplete.

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?

The description adds partial meaning to the includeContent parameter by linking it to 'full markdown content', but the id parameter is only described as 'by id' with no further detail. With 0% schema coverage, this provides some compensation but not enough for full clarity.

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 clearly states the tool retrieves a saved link or note by ID, which is a specific action on a specific resource. It distinguishes from sibling tools like list_saves (listing all) and search_saves (searching), as it targets a single item by ID.

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 such as list_saves or search_saves. The description does not mention prerequisites or conditions, leaving the agent to infer usage from the name alone.

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