Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAPER_SEARCH_CACHENoLocal SQLite cache file path./tmp/paper_search_cache.db
SEMANTIC_SCHOLAR_API_KEYNoSemantic Scholar API key. Recommended to avoid rate limits.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_literatureC

Search open scholarly literature across configured sources.

plan_literature_searchC

Plan source routing and ranking without running a live search.

get_workB

Get a work by identifier (DOI, PMID, PMCID, arXiv, etc.).

resolve_identifiersC

Resolve a list of identifiers across sources and return merged records.

get_source_statusB

Return the health status of all configured sources.

lookup_meshC

Lookup MeSH descriptors for a biomedical term.

find_related_articlesC

Find PubMed related article PMIDs.

convert_identifiersC

Convert DOI/PMID/PMCID identifiers through the NCBI ID converter.

search_literature_signalsC

Search biomedical literature signals via PubTator3.

expand_from_workC

Expand from a known work by citations, references, or similar papers.

export_recordsC

Export a list of works to a supported format.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 11 tools

Disambiguation3/5

Several tools have overlapping purposes: search_literature vs. search_literature_signals both search, resolve_identifiers vs. convert_identifiers both handle IDs, and find_related_articles vs. expand_from_work both find related works. Descriptions clarify differences, but confusion is possible.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (search_literature, get_work, resolve_identifiers, export_records). Minor deviations like expand_from_work (verb-preposition) and lookup_mesh (terse) exist but do not disrupt overall predictability.

Tool Count5/5

With 11 tools, the set is well-scoped for a literature search server. Each tool serves a distinct step in discovery, retrieval, and export without unnecessary redundancy or bloat.

Completeness4/5

The tool set covers the core scholarly search workflow: planning, searching, retrieving by ID, converting identifiers, expanding from known works, and exporting. Minor gaps exist, such as full-text retrieval or advanced citation analysis, but they are not critical for the stated purpose.

Maintenance

ActivityStale
ResponsivenessNo issues