Skip to main content
Glama
alshyra

Sherlock's second brain

by alshyra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SECOND_BRAIN_DATA_DIRNoRoot data directory for cases + kb + vector~/second-brain-data

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
case_createA

Create an investigation case. Use this when a topic is not yet validated.

tags and references are comma-separated strings.

case_getA

Read a case by its id (e.g. case-2026-08-07-001).

case_listA

List cases, optionally filtered by status (open/in_progress/resolved/abandoned) and tag.

case_searchB

Semantic search across cases and KB. Use this FIRST when debugging or planning.

case_updateA

Append to a case.

fields supports:

  • finding (str): append to findings

  • step_action (str): append a step (with optional step_result)

  • step_result (str): result for the step being appended

  • conclusion (str): set conclusion

  • hypothesis_statement / hypothesis_test: append a hypothesis

  • tags (list[str]) / references (list[str]): replace lists

case_add_evidenceC

Attach a piece of evidence (log excerpt, output, note) to a case.

case_set_statusA

Change a case status: open / in_progress / resolved / abandoned.

case_promoteA

Promote a resolved case into validated KB: target = fiche or skill.

Generates the MD/SKILL.md from the case, writes it to the KB and marks the case.

fiche_listA

List validated fiches (slugs).

fiche_readC

Read a validated fiche by slug.

fiche_writeA

Create or overwrite a fiche. Prefer case_promote for validated knowledge.

skill_listB

List validated skills (slugs).

skill_readA

Read a validated skill by slug.

index_rebuildA

Rebuild the vector index from all source files. Returns doc count.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 14 tools

Disambiguation4/5

Tools are mostly distinct, but case_update and case_add_evidence both append to a case, and case_promote vs fiche_write both create fiches, which could cause some confusion. The descriptions clarify the intended use, but the boundaries are not perfectly sharp.

Naming Consistency5/5

All tools follow a consistent pattern of domain prefix (case_, fiche_, skill_, index_) followed by an action verb (get, list, search, update, promote, etc.). The naming is uniform and predictable across the entire set.

Tool Count5/5

14 tools is within the ideal range for a specialized knowledge management server. Each tool covers a distinct aspect of the workflow, and the count feels neither sparse nor bloated.

Completeness4/5

The case lifecycle is well covered (create, read, list, search, update, add evidence, set status, promote), and the fiche/skill read/list operations support retrieval. However, there are no delete operations for cases or knowledge artifacts, and skills lack a direct write/update tool, which are minor but notable gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources