Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMOS_BASE_URLNoThe base URL of your Memos instancehttp://localhost:5230
MEMOS_API_TOKENNoYour Memos API authentication token (optional for public instances)

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_memosA

Search for memos with optional filters.

Args: query: Text to search for in memo content creator_id: Filter by creator user ID tag: Filter by tag name visibility: Filter by visibility (PUBLIC, PROTECTED, PRIVATE) limit: Maximum number of results to return (default: 10) offset: Number of results to skip (default: 0)

Returns: JSON string containing the list of matching memos

create_memoB

Create a new memo.

Args: content: The content of the memo (supports Markdown) visibility: Visibility level - PUBLIC, PROTECTED, or PRIVATE (default: PRIVATE)

Returns: JSON string containing the created memo details

update_memoB

Update an existing memo.

Args: memo_uid: The UID of the memo to update (e.g., "abc123") content: New content for the memo (optional) visibility: New visibility level - PUBLIC, PROTECTED, or PRIVATE (optional) pinned: Whether to pin the memo (optional)

Returns: JSON string containing the updated memo details

get_memoA

Get a specific memo by its UID.

Args: memo_uid: The UID of the memo to retrieve (e.g., "abc123")

Returns: JSON string containing the memo details

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create_memo for creation, get_memo for retrieval by UID, search_memos for filtered searching, and update_memo for modifications. The actions (create, get, search, update) target the same resource (memos) but operate in non-overlapping ways, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'memo' as the noun: create_memo, get_memo, search_memos, update_memo. The pattern is uniform throughout, using snake_case and clear action verbs, making the set predictable and easy to understand.

Tool Count5/5

With 4 tools, this server is well-scoped for a memos management system. Each tool earns its place by covering essential CRUD operations (create, get, update) plus search functionality, which is appropriate for the domain without being overly sparse or bloated.

Completeness4/5

The tool set covers core CRUD operations (create, get, update) and search, but lacks a delete_memo tool for full lifecycle coverage. This minor gap might require workarounds for deletion tasks, though the existing tools support most common workflows effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues