shebanq-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BHSA_SQLITE | Yes | Path to the BHSA SQLite database file (e.g., data/bhsa.sqlite3) | |
| LLM_PROVIDER | No | LLM provider: 'anthropic' (default) or 'none' | anthropic |
| ANTHROPIC_API_KEY | No | API key for Anthropic LLM. Required unless LLM_PROVIDER is set to 'none'. |
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 |
|---|---|
| lookup_featureB | Look up a BHSA feature: its gloss and valid values. |
| run_mqlA | Validate and run a read-only MQL query; return the query and glossed results. Only read-only queries (SELECT/GET) are accepted. Quoting rule (getting it wrong fails typechecking): enumeration features compare UNQUOTED (sp=verb, vs=nif); string features compare QUOTED (lex='BR>['). Verb lexemes carry a trailing '['. Call lookup_feature(name) to check a feature's kind/values. |
| run_tfA | Validate and run a Text-Fabric search template; return glossed results. A template is one object per line, indentation = containment, constraints as unquoted feature=value pairs (sp=verb, lex=BR>[). Put the object you want results for on the LAST line. Call lookup_feature(name) to check a feature's values. Pinned to the BHSA 2021 release. |
| to_citable_mqlA | Convert a Text-Fabric search template to equivalent MQL for SHEBANQ. Deterministic, no model involved: indentation becomes brackets, spaces become AND, string features get quoted from the catalogue. Use this to turn a notebook query into a citable SHEBANQ saved query. Templates using TF constructs beyond ' feature=value ...' lines are refused with an explanation. The mirror of to_tf_template. |
| to_tf_templateA | Convert an Emdros MQL query to the equivalent Text-Fabric search template. Deterministic, no model involved: brackets become indentation, AND becomes a space, quoted string values lose their quotes. GET clauses are dropped with a note (TF results expose all features). MQL using OR, NOT, FOCUS, or sequence operators is refused with an explanation. The mirror of to_citable_mql. |
| search_bhsaA | Answer a plain-language question about the Hebrew Bible. With server-side translation enabled, returns generated MQL + results. On the public deploy (no server-side LLM) it returns a concise MQL-writing primer so you compose a read-only query yourself and call run_mql. Use the write-mql prompt for the full feature reference. The response also carries the query's Text-Fabric equivalent, derived deterministically from the MQL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| write_mql | Compose a read-only BHSA MQL query for a plain-language question. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tools are largely distinct: lookup_feature for metadata, run_mql and run_tf for executing queries, search_bhsa for plain-language queries, and two conversion tools. However, search_bhsa's output sometimes overlaps with run_mql/run_tf when it generates MQL, causing slight potential confusion.
Naming follows a consistent verb_noun pattern (lookup_feature, run_mql, run_tf, search_bhsa) with a 'to_' prefix for conversion tools (to_citable_mql, to_tf_template). Minor inconsistency in the naming of search_bhsa (domain name instead of resource) but overall pattern is clear.
6 tools is appropriate for the server's purpose of querying the BHSA Hebrew Bible data. It covers execution, conversion, and metadata lookup without being overwhelming or too sparse.
The tool surface covers core workflows: query execution in two formats, conversion between them, plain-language search, and feature metadata. Minor gaps exist (e.g., no tool to list object types or manage sessions), but the set is reasonably complete for read-only querying.