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
record_lessonA

Record a lesson into the persistent store. Returns the new lesson.

recall_lessonsA

Recall top-k lessons matching query (FTS5 retrieval).

recent_lessonsB

Return the most-recent lessons (chronological).

by_categoryA

Return lessons filtered by category (most-recent first).

mark_lesson_usedA

Bump times_used on a lesson — call when you actually applied it.

store_statsB

Return total and per-category counts.

analyze_pathB

Run deterministic static checks. Returns Markdown report + raw findings list.

get_conventionsA

Return the full AGENTS.md content (auto-curated project conventions).

set_conventionA

Append a new convention to AGENTS.md and return its line number.

propose_fixA

Suggest a fix sketch by combining the issue with k similar past lessons.

This is deterministic text-stitching — no LLM is called. The orchestrator (which has the LLM) reads the result and decides whether to apply.

reflectA

Return a Markdown draft of new AGENTS.md conventions from recent lessons.

The orchestrator curates which lines to apply by calling set_convention() for each. The agent itself does no LLM calls — the draft is a deterministic aggregation of stored signals (category breakdown, frequently-recurring tags, never-recalled lessons, top-referenced).

lint_checkA

Run external linter(s) and test runner; return findings + summary.

Each tool maps to the same Finding shape the built-in analyzer uses, with source set to the tool name (e.g. 'ruff', 'pytest'). Tools not on PATH are skipped with a reason field, not raised as errors.

doctor_toolA

Same report as smart-agent doctor CLI, returned as a string.

Useful when the orchestrator wants to spot-check the installation during a session.

health_checkA

Return a structured JSON snapshot for monitoring.

Fields: ok boolean — always true if the store could be opened schema_version stored schema_version current_schema version this code expects wal_mode WAL / journal-mode status db_path absolute path to the SQLite file db_size_bytes file size on disk lessons_total row count in the lessons table conventions_path where AGENTS.md lives conventions_writable bool — whether AGENTS.md can be appended to

Use this for liveness/readiness checks, not for hot-path validation.

Prompts

Interactive templates invoked by user choice

NameDescription
code_reviewStructured prompt that asks the orchestrator to review code thoroughly.

Resources

Contextual data attached and managed by the client

NameDescription
memory_recentMarkdown list of the most recent 20 lessons.
memory_statsMarkdown summary of the lesson store.
conventions_currentFull content of the project AGENTS.md.

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/cbuntingde/smart-agent'

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