YRB-HES Evidence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YRB3_MCP_DATABASE_URL | No | Optional database URL. Defaults to a local Unix socket connection to dbname=rag_sag. |
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 |
|---|---|
| healthcheckB | Check PostgreSQL, yrb3_v3 tables, read-only identity and current row counts. |
| get_document_overviewB | Return metadata, abstract screening, heading, Subchunk, SAG and spatiotemporal counts for one document. |
| search_evidenceB | Search YRB3 evidence with exact if_yrbhg gate, lexical Subchunk recall, Event expansion and spatiotemporal attachment. |
| compare_evidenceA | Build bounded cross-paper comparison rows with claims, entities, spatiotemporal evidence and source locators. |
| get_subchunk_contextB | Return one Subchunk, its title path, adjacent context and linked Event/spatiotemporal evidence. |
| search_entityA | Search canonical SAG entities by name, alias key and optional entity type. |
| expand_entityC | Expand one canonical entity to linked Event, Subchunk, spatiotemporal evidence and verified edges. |
| get_spatiotemporal_evidenceB | Query structured spatial and temporal evidence with document, Subchunk and research-area filters. |
| trace_sourceB | Trace an Event, Subchunk or spatiotemporal evidence ID back to Markdown content and hashes. |
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 9 tools
Each tool targets a distinct operation: document overview, subchunk context, evidence search, comparison, entity search, entity expansion, spatiotemporal query, source tracing, and health check. Though search_evidence and get_spatiotemporal_evidence both deal with evidence, the former is full-text with event expansion while the latter is structured query with filters, so they remain clearly distinguishable.
Most tools follow a clear verb_noun pattern (get_document_overview, search_evidence, compare_evidence, expand_entity, trace_source). The lone exception is 'healthcheck', which is a single compound noun rather than a verb-led name, making it a minor deviation from the otherwise consistent convention.
With 9 tools, the server is well-scoped for its purpose. Each tool addresses a distinct aspect of evidence retrieval and exploration, from document-level overview to fine-grained spatiotemporal queries and source tracing, without unnecessary redundancy or bloat.
The read-only evidence surface is fairly comprehensive: it covers document overview, subchunk context, evidence search, comparison, entity retrieval/expansion, spatiotemporal filtering, and source tracing. A minor gap is the lack of a direct document listing method, though search_evidence can partially compensate by returning relevant documents.