turnwise
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_transcriptA | Normalize a transcript into speaker turns and compute structural metrics: turn counts, airtime share per speaker, airtime concentration, and question rate. Run this when a transcript's format is uncertain, to confirm speakers were detected correctly before scoring. |
| transcribe_audioA | Transcribe a single audio or video recording to WebVTT using a local speech model. Audio stays on this machine. A mixed track cannot be reliably split by speaker, so the result omits speaker labels and cannot produce per-speaker scores. For those, record one file per participant and use transcribe_session. |
| transcribe_sessionA | Transcribe a folder of per-participant recordings and merge them into one speaker-labeled transcript ordered by timestamp. Each file contains exactly one person, so speaker attribution is exact. This is the recommended path for anything that needs per-speaker scores. In Zoom, enable Settings > Recording > 'Record a separate audio file for each participant'. Speaker names come from the filenames. |
| check_audio_supportA | Report which local speech-to-text backends and media tools are installed, with install instructions if none are. Use this before attempting transcription so a missing dependency surfaces as a clear answer. |
| score_conversationA | Score a conversation for bridging quality. Returns a 0-4 score per speaker per indicator (receptiveness, perspective-taking, contempt, curiosity, concession, personal disclosure), each with quoted evidence anchored to turn numbers, a confidence value, and deterministic airtime metrics. Set arc_segments to 3 to see how the conversation changed from opening to close. |
| extract_evidenceA | Return every pattern match the instrument found, with the quote and the rule that fired, plus the turns where nothing matched. Use this when the reading matters more than the number: you confirm or reject each candidate yourself, catching sarcasm and quoted speech that a word list scores wrong, and catching behavior in the unmatched turns that no pattern covers. This is the tool for producing a defensible qualitative summary. |
| compare_conversationsA | Score two transcripts and lay them side by side with the difference on each indicator. Use for before/after comparisons: the same group early and late in a program, one workshop format against another, or a facilitator's first session against their tenth. |
| analyze_cohortA | Combine scores from multiple conversations into one report: per-indicator means, spread, and optional group comparison with effect size. This is the tool that produces something a funder can read. Pass the structured score objects returned by score_conversation. |
| explain_indicatorA | Return the full rubric for one indicator: what it measures, what counts as evidence, what does not count, the 0-4 anchors, the thresholds, what the score cannot tell you, and the research behind it. Use whenever someone asks what a score means or challenges one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| score_workshop | Score one transcript, verify the evidence, and write it up. |
| funder_report | Score a set of transcripts and aggregate them into a reportable summary. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| rubrics | The indicator definitions, marker lists, scale anchors, limitations, and citations, as JSON. This is the published measurement definition. Any client can read it to check what the numbers mean. |
| methodology | What these scores are, what they are not, how confidence is computed, and what would be needed to call them validated. Read before putting numbers in a report. |
TDQS
Scored across 9 tools
Each tool targets a distinct stage in the analysis pipeline, from environment checks to transcription, parsing, scoring, evidence extraction, comparison, cohort analysis, and rubric explanation. No two tools share the same purpose, and descriptions clearly differentiate similar operations like transcribe_audio vs transcribe_session.
All tool names follow a consistent verb_noun snake_case pattern (e.g., check_audio_support, transcribe_session, score_conversation). This makes the action and target immediately clear, and there are no stylistic deviations.
With 9 tools, the set is well-scoped and each tool earns its place. The count fits within the ideal 3-15 range and covers the full workflow without redundancy.
The server covers the entire lifecycle from pre-transcription checks to group-level analysis and rubric explanation. There are no obvious gaps: transcription, parsing, scoring, qualitative evidence review, comparison, and cohort aggregation are all represented.