ask-pb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASK_PB_DATA_DIR | No | Set the data directory for the server. The default is ./data. Pass --data-dir before the subcommand for a stable absolute location. | ./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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_bike_evidenceA | Find timestamped transcript segments using keywords (all query words must match). Use short product/topic queries, not full questions. Results include source and transcript provenance. Search is lexical, not exhaustive thematic analysis. Maximum 50 results. |
| get_evidenceB | Get original transcript wording and citation metadata for a search result. A stale transcript flag means the feed's audio URL changed after transcription. |
| list_episodesA | Browse episode metadata, transcription availability, and errors. Maximum 500 per page. |
| get_coverageA | Get indexed episode counts, feed check times, and limitations. Metadata is not evidence. |
| get_episode_passagesA | Read surrounding transcript passages at or after a time, including overlapping passages. Paginate using the last passage end time. Maximum 50 passages. Returns original wording. |
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 5 tools
Each tool targets a distinct step in the workflow: searching transcripts, retrieving evidence details, listing episodes, checking coverage, and reading passages. No two tools appear to serve the same purpose; descriptions clearly differentiate them.
All tool names follow a consistent verb-object snake_case pattern (search_, get_, list_)) with clearly descriptive objects. The verbs are appropriate for the action, and no mixed conventions or vague generic names are present.
Five tools is well within the ideal range for a focused read-only evidence retrieval server. Each tool covers a necessary part of the search-and-retrieval workflow without bloat or missing essentials.
The tool surface covers the full workflow: search across transcripts, fetch exact evidence, browse episode metadata, check indexing coverage, and read surrounding passages. No obvious dead ends or missing operations for the stated purpose.