starbuck-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUARTO_PATH | No | Path to Quarto when it is not on the PATH. | |
| NCBI_API_KEY | No | Higher request rate for PubMed. | |
| STARBUCK_EMAIL | No | Contact address for the services. | |
| OPENALEX_API_KEY | No | OpenAlex API key. | |
| ZOTERO_CONTACT_EMAIL | No | Contact address for the services (alternative to STARBUCK_EMAIL). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_manuscriptA | Check every cited reference of a Markdown or Quarto manuscript and write a report. Reads [@citekey] citations with the bibliography named in the YAML header (or given here), or numbered [1] citations with a numbered list under a References/Sources heading. Writes -references.qmd and .json to report_dir (default: _starbuck next to the manuscript) and renders formats (default ["html"]; "docx" for Word). Also returns the count and the first 10 sentences that state a finding without a citation. |
| check_referencesA | Check references given directly: an identifier, citation details, or both. With citation details, level 2 compares them with the record; with an identifier alone, only levels 1 and 3 apply. Use this for the sources of a report you wrote. |
| prepare_claimsA | Level 4, step 1. Checks the references (levels 1 to 3) and returns, for each citing sentence, the best passages of the cited source (open-access full text, a local text file from texts {citekey: path}, or the abstract). Judge each claim from its passages, then call record_claims. Results come in pages: use offset and limit; total gives the number of claims. Writes -references.json and -claims.json to report_dir (default _starbuck). |
| record_claimsA | Level 4, step 2. Checks each quoted passage against the source text (a quote that is not there turns the verdict into cannot_assess), adds the verdicts to the report and renders it. Give the verdicts of all claims from prepare_claims in one call. |
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 4 tools
check_manuscript and check_references both check references, but their inputs differ clearly (manuscript vs. direct reference details), and the descriptions distinguish them. prepare_claims and record_claims are explicitly sequential steps, leaving little ambiguity.
All four tools use a consistent snake_case verb_noun pattern: check_manuscript, check_references, prepare_claims, record_claims. No mixed conventions or vague verbs.
Four tools is well-scoped for a specialized citation- and claim-checking workflow. Each tool maps to a distinct stage or input mode, and none feels redundant.
The surface covers manuscript checking, direct reference checking, claim preparation, and claim recording, which is strong lifecycle coverage for this domain. Minor gaps exist around report retrieval or configuration management, but agents can work around them.