Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LIBAPPS_TIMEOUTNoHTTP timeout (seconds)30
LIBAPPS_API_BASENoRegion host: lgapi-{us,ca,eu,au}.libapps.com. Other hosts need LIBAPPS_ALLOW_CUSTOM_API_BASE=1https://lgapi-us.libapps.com
LIBAPPS_CLIENT_IDYesOAuth client ID for the LibApps v1.2 app
LIBAPPS_LOG_LEVELNoLog level; logs go to stderr onlyWARNING
LIBAPPS_MAX_CHARSNoDefault markdown budget per get_guide_content call20000
LIBAPPS_HTML_FETCHNoRead page content from public guide pages. 0 falls back to unplaced API text1
LIBAPPS_USER_AGENTNoUser agent for all requestslibapps-mcp/0.1.0 (+repo URL)
LIBGUIDES_SITE_URLNoPublic site origin, used for page fetches. Default derived from guide URLs
LIBAPPS_EXPOSE_EMAILNoInclude the public-profile contact email for librarians0
LIBAPPS_CACHE_TTL_REFNoCache lifetime (seconds) for subjects, accounts, and A-Z86400
LIBAPPS_CLIENT_SECRETYesOAuth client secret for the LibApps v1.2 app
LIBAPPS_CACHE_TTL_LISTNoCache lifetime (seconds) for the guide list1800
LIBAPPS_INCLUDE_PRIVATENoInclude Private guides and hidden pages/boxes0
LIBAPPS_MAX_CONCURRENCYNoMaximum concurrent upstream requests4
LIBGUIDES_ALLOWED_HOSTSNoExtra comma-separated hosts the page fetcher may use
LIBAPPS_CACHE_TTL_CONTENTNoCache lifetime (seconds) for guide outlines, pages, and searches900
LIBAPPS_ALLOW_CUSTOM_API_BASENoSet to 1 to allow custom API base hosts other than the default region hosts

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_guidesA

Search published research guides. With a query, uses the site's relevance-ranked full-text guide search (source 'server'); without one, or if that search fails, matches guide names, subjects, descriptions, and owner names locally (source 'local'). Optional filters: subject (name or id), owner (public profile name), guide_type (e.g. subject, course, topic, general, or type id). Paginate with limit (max 50) and offset; next_offset is null when done.

get_guideA

Get a guide's metadata and its full page outline: a tree of pages and sub-pages with page_id, name, url, and box names. Use get_guide_content with a page_id to read a page.

get_guide_contentA

Read a guide page as markdown, one entry per content box in display order. Defaults to the guide's first page; pass page_id (from get_guide or the returned outline) for another page, and include_subpages=true to add its sub-pages. source: auto (default), html (public page), or api (unplaced text blocks for the whole guide). Output is capped at max_chars; continue with offset=next_offset.

list_subjectsA

List the site's guide subjects (id, name, slug). By default only subjects that have published guides.

search_databasesA

Search the A-Z database list by name, alternate names, vendor, and description. Optional filters: subject and az_type (name or id). Without a query, lists databases alphabetically. Paginate with limit (max 50) and offset.

get_databaseA

Get one A-Z database by id, with its full description and access URL.

find_subject_librariansA

Find librarians with a public profile for a subject (name or id). Returns names, titles, profile links, and contact details they chose to show publicly.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions, with search_guides (find), get_guide (metadata+outline), and get_guide_content (page text) forming a coherent retrieval pipeline. The get_guide vs get_guide_content pair is the only mild overlap, but descriptions clearly delineate their roles.

Naming Consistency5/5

All seven tools follow a consistent verb_noun pattern (list_subjects, search_guides, get_guide, get_guide_content, search_databases, get_database, find_subject_librarians). Verb variety (list/search/get/find) reflects genuinely different operations rather than inconsistency.

Tool Count5/5

Seven tools is well-scoped for an A-Z database and research guide server, with each tool earning its place across the subjects, guides, databases, and librarians domains. No redundant or trivial tools.

Completeness4/5

The surface covers the core read workflows: subjects, guide discovery and content, databases, and subject librarians, with pagination handled throughout. As a read-only surface it lacks write operations and some minor browse helpers (e.g., listing guide types), but core research workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues