StudyDiff
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | API key for Anthropic's Claude API. Only needed for the `compare_studies` tool; `list_examples` and `compare_example` work without it. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_studiesA | Explain WHY two scientific papers reach different conclusions. Extracts each study design (species, model, intervention, assay, dose, timing, endpoint, sample size, statistic, finding, limitations), verifies every extracted value against the source text with deterministic grounding, then lists the design differences that could drive the disagreement (unranked, plus the dimensions that are identical in both and so ruled out) and suggests what evidence would resolve it. Every claim is traced to a verbatim quote; unsupported fields are returned as "not reported" rather than guessed. Never picks a winner. Each paper is given as {id} (PMID or DOI) or {text}. Requires ANTHROPIC_API_KEY – use compare_example for a no-key demonstration. |
| compare_exampleA | Run one of StudyDiff's built-in worked examples – real, famous contradictions with verbatim abstracts. Runs fully offline against cached papers: no API key and no network needed, so it is the quickest way to see the grounded output. Options: "mouse-inflammation" (Seok 2013 vs Takao 2015 – same datasets, opposite conclusions), "resveratrol-sirt1" (Howitz 2003 vs Beher 2009 – an assay artifact), "treg-stability" (Zhou 2009 vs Rubtsov 2010 – stable vs unstable Treg lineage, driven by the fate-mapping method). |
| list_examplesA | List StudyDiff's cached worked examples (real published contradictions) that can be run with compare_example without an API key. |
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 3 tools
Each tool has a clearly distinct purpose: compare_example runs a pre-cached demonstration, list_examples enumerates those demonstrations, and compare_studies handles user-supplied papers. There is no overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern with snake_case (compare_example, list_examples, compare_studies). The shared 'compare' prefix is semantically appropriate and does not create confusion.
With 3 tools, the surface is tightly scoped to the server's purpose: list examples, run an example, and run a custom comparison. Each tool earns its place and the count is well within the ideal 3-15 range.
The tool set fully covers the intended workflow: users can discover available examples, run them for quick demonstration, and perform a full custom analysis on their own papers. There are no missing operations or dead ends for the stated domain.