Skip to main content
Glama
Sign In
own-mcp-server

own-mcp-server

by mayo-byte07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Add Note

add_note

Persist a brief note with a title to disk, keeping it available across server restarts.

Instructions

Save a short text note with a title, persisted to disk so it survives server restarts.

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort title for the note
contentYesThe note's content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description must carry behavioral disclosure on its own. It does so by stating that notes are persisted to disk and survive restarts, which is a non-obvious side effect. It stops short of describing return values or duplicate handling, but covers the core behavior.

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?

One sentence, front-loaded with the action, with every phrase earning its place. There is no filler or redundancy.

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

Completeness3/5

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

The tool is simple and the schema covers both parameters, so the description covers the essential operation and persistence. However, with no output schema, the description doesn't say what the tool returns after saving, which an agent might need to handle the result.

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 description coverage is 100%, so the parameters are already fully documented. The description's phrase 'with a title' adds no new meaning 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?

States a specific verb ('Save') and resource ('short text note'), with a clear scope. The persistence detail further distinguishes it from ephemeral operations, and the sibling names make its role obvious.

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

Usage Guidelines3/5

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

The description implies when to use the tool – to save a note – but never contrasts it with alternatives like list_notes or delete_note, nor states when not to use it. The guidance is implicit rather than explicit.

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