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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_knowledgeA

Search published knowledge items and packages using hybrid semantic + lexical retrieval.

Args: query: Natural language query to search knowledge items for. item_types: Optional filter for specific item types (e.g. CONCEPT, PROCEDURE, RULE). min_confidence: Minimum confidence score filter (0.0 to 1.0). limit: Maximum number of ranked results to return (default 10).

get_knowledgeA

Fetch a specific knowledge item by its UUID, including bound evidence citations and relationships.

Args: knowledge_id: UUID string of the knowledge item.

get_evidenceA

Retrieve raw source evidence snippet, timestamps, video association, and confidence.

Args: evidence_id: UUID string of the evidence record.

search_sourcesA

Search ingested sources, playlists, and videos by title, URL, or metadata.

Args: query: Search term for source title, channel, or URL. limit: Maximum number of results to return.

get_sourceA

Get source/video/playlist details, ingestion status, and published package versions.

Args: source_id: UUID string of the source, playlist, or video.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource and action: fetching by ID vs searching by query, and separating knowledge, evidence, and sources. There is no overlap or ambiguity between the five tools.

Naming Consistency5/5

All tool names follow the same verb_noun pattern using either 'get_' or 'search_' prefixes. The naming is perfectly consistent and predictable.

Tool Count5/5

With 5 tools, the server is well-scoped for a knowledge and evidence retrieval system. Each tool contributes a distinct function and none are redundant or excessive.

Completeness4/5

The set covers retrieval and search for knowledge, evidence, and sources comprehensively. However, it lacks any mutation or ingestion operations, which may be a minor gap if the server is intended to manage the full lifecycle.

Maintenance

ActivitySlowing
ResponsivenessNo issues