Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_noteA

Create a new note and return it, including the generated id to use in later calls.

Titles must be unique case-insensitively; creating a note whose title already exists is an error, so if the user wants to change an existing note, use update_note.

get_noteA

Read one note in full by id.

Use this whenever you need a note's complete body — list_notes previews are cut off after 120 characters. Ids come from list_notes or create_note; this tool does not accept titles.

list_notesA

List notes, most-recently-updated first, as previews.

Pass query to filter to notes whose title or body contains that text (case-insensitive substring, not fuzzy or semantic — prefer one distinctive word over a whole phrase, and drop the filter entirely to browse everything).

Each entry carries id, title, preview, content_truncated, content_length, created_at, and updated_at. total_count is the number of matches, which exceeds the returned notes when limit cut the page short.

update_noteA

Overwrite the title and/or content of an existing note and return the updated note.

This REPLACES whatever you pass; it does not merge. Omit a field (or pass null) to leave it alone. To add to a note's body without losing the current text, call get_note first and pass the full combined text as content.

delete_noteA

Permanently delete the note with the given id and return what was removed.

This cannot be undone and the note's content is not recoverable, so confirm the id with list_notes or get_note before calling when the user identified the note by description rather than by id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool maps to one distinct resource action (create, get, list, update, delete), with no overlapping operations. The descriptions reinforce boundaries by explaining when to use get_note over list_notes and create_note over update_note.

Naming Consistency5/5

All tool names follow the same verb_note pattern: create_note, get_note, list_notes, update_note, delete_note. list_notes is pluralized because it returns a collection, but the convention is otherwise uniform and predictable.

Tool Count5/5

Five tools form a tightly scoped set for a notes server: one create tool, one read tool, one list tool, one update tool, and one delete tool. Each tool earns its place and the count is ideal for the domain.

Completeness5/5

The tool surface covers the full note lifecycle with no dead ends: create, list, read by id, update, and delete. The update tool's replace-only behavior is mitigated by explicit guidance to call get_note first, so agents have a complete workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues