Skip to main content
Glama
louis49

Melchizedek

by louis49
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

__USAGE_GUIDE

Read-onlyIdempotent

Guides you through Melchizedek's retrieval pattern and tool usage. Covers search, context, full content, and session management.

Instructions

melchizedek v1.0.2 — Persistent memory for Claude Code with hybrid search (BM25 + dual embeddings) + reranking.

Corpus: empty (no sessions indexed yet).

Available tools (16):

  • m9k_search: Find past conversations (BM25 + text vectors + code vectors, fused via RRF)

  • m9k_context: Get a chunk with surrounding conversation context

  • m9k_full: Get complete chunk content by IDs

  • m9k_sessions: Browse indexed sessions

  • m9k_file_history: Find conversations that touched a specific file

  • m9k_errors: Find past solutions for error messages

  • m9k_save: Store important notes for future recall

  • m9k_similar_work: Find past approaches to similar tasks (bonus for complex work)

  • m9k_forget: Permanently remove a chunk from memory

  • m9k_info: Memory index information, corpus size, search pipeline status, usage metrics, embedding worker state

  • m9k_config: View or update plugin configuration

  • m9k_delete_session: Remove a session from the index

  • m9k_ignore_project: Exclude a project from indexing (optionally purge existing data)

  • m9k_unignore_project: Re-enable indexing for a previously ignored project

  • m9k_restart: Restart the MCP server to load fresh code after rebuild

RETRIEVAL PATTERN (use this order):

  1. m9k_search(query) → compact results, current project and session boosted (use order="date_asc" to find first occurrence)

  2. m9k_context(chunkId) → surrounding conversation

  3. m9k_full([chunkIds]) → complete content if needed

SPECIALIZED SEARCH:

  • m9k_file_history(filePath) → before modifying any file

  • m9k_errors(errorMessage) → when you hit an error

  • m9k_similar_work(description) → at the start of a complex task

MANAGE:

  • m9k_info() → check corpus size, search pipeline, usage metrics

  • m9k_config() → view or change plugin configuration

  • m9k_delete_session(sessionId) → remove a session from the index

  • m9k_ignore_project(project) → exclude a project from indexing

  • m9k_unignore_project(project) → re-enable indexing for a project

  • m9k_restart() → restart server after npm run build

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

C2.1/5.0
Behavior2/5

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

Annotations (readOnlyHint, idempotentHint, non-destructive) provide basic safety info, but the description does not explain what the tool actually does when called (e.g., returns a text guide). Without an output schema, the description should clarify the behavioral outcome, but it focuses on system capabilities instead.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long, including version info, corpus status, and full listings of sibling tools. While this might be useful as a reference, it is not concise for a tool definition. Key information about the tool itself is buried in a wall of text.

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 the tool has no parameters, no output schema, and is a guide, the description should clearly state what invoking it returns or achieves. It omits this critical information, instead presenting a system overview. The description is incomplete for an agent to understand the tool's purpose.

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

Parameters4/5

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

No parameters exist, so the description has no need to add parameter semantics. The input schema fully covers this. Baseline for zero parameters is 4, and the description does not mislead or omit any needed param info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name '__USAGE_GUIDE' suggests it provides guidance, but the description reads as a system overview rather than explicitly stating what this tool does when invoked. It lacks a clear verb+resource statement like 'Returns a usage guide for the melchizedek memory system.' The description is more about the system than the tool itself.

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

Usage Guidelines1/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. It does not explain scenarios where invoking the usage guide is appropriate, nor does it contrast with sibling tools. The description lists sibling tools but provides no selection criteria or context for using this specific tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/louis49/melchizedek'

If you have feedback or need assistance with the MCP directory API, please join our Discord server