Skip to main content
Glama
Sign In
@memlane/mcp

@memlane/mcp

by danii1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

update_note

Update the title or markdown body of an existing note by specifying its ID.

Instructions

Update a note's title and/or markdown body

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

Input Schema

NameRequiredDescriptionDefault
idYes
titleNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether updates are incremental or replace existing fields, whether authorization is required, or what happens to omitted fields. The description only says 'Update' without elaboration.

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?

A single, concise sentence with no extraneous information. Efficiently communicates the core operation.

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 no annotations, no output schema, and triple parameters, the description lacks crucial context: return value, behavior for omitted fields, error handling, and prerequisites. Notable gaps remain.

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

Parameters2/5

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

Schema description coverage is 0%. The description adds minimal meaning by mapping 'title' and 'markdown body' to the title and content parameters, but it does not explain formats (e.g., markdown syntax) or that 'id' is required. The added value is marginal.

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?

Clearly states the verb 'Update' and the resource 'note', specifying the fields affected ('title and/or markdown body'). This distinguishes it from sibling tools like create_note (creation) and list_saves (listing).

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 on when to use this tool versus alternatives (e.g., create_note for new notes). No exclusion criteria or context hints provided.

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