Samuraizer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| normalize_audioB | Normalize an audio file to 16kHz mono PCM WAV format required by Whisper. |
| transcribe_audioB | Transcribe an audio file using whisper.cpp. Returns the transcript text. |
| summarize_transcriptC | Generate a concise meeting summary from transcript text. |
| extract_action_itemsA | Extract action items from a meeting transcript. Returns a JSON list of tasks with owner and due date. |
| extract_decisionsB | Extract confirmed decisions from a meeting transcript. Returns a JSON list of decisions. |
| process_recordingB | Run the full Samuraizer pipeline on an audio file. Returns summary, action items, decisions, and output file paths. |
| search_meetingsA | Search meetings by summary text, name, action items, and decisions. Transcripts are not searched — use get_meeting for those. Returns ranked results with snippets. |
| list_meetingsA | List all processed meetings, sorted newest first. Optionally limit results. |
| get_meetingB | Retrieve the full processed output for a specific meeting by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose, from normalization and transcription to summarization, extraction, and meeting management. The separate extraction tools for action items and decisions avoid overlap, and process_recording serves as a composite operation without ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., normalize_audio, transcribe_audio, list_meetings), making it predictable and easy to understand the function of each tool.
With 9 tools, the count is well-suited to the domain of audio processing and meeting summaries. It covers the essential steps of the pipeline and meeting retrieval without being excessively large or minimal.
The tool set covers the full workflow from raw audio normalization to transcription, summarization, extraction of action items and decisions, and includes a composite processing tool. Retrieval, search, and listing functions complete the necessary operations for managing processed meetings.