Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PYTHONPATHYesThe absolute path to the librarian directory, required for the python interpreter to locate the server modules.

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_wikipedia_pagesB

Search for Wikipedia pages on a certain word/topic and return the first 5 results with information to help choose the most relevant one

get_wikipedia_page_summaryB

Get a quick summary of a Wikipedia page - lighter version of get_wikipedia_page_info

get_wikipedia_page_sectionsA

Get a list of the sections on a Wikipedia Page. Its useful for when a page on wikipedia is too large and the LLM can query for the available sections to it to get only necessary information

get_wikipedia_page_sections_infoC

Get detailed sections information about a specific Wikipedia page

get_wikipedia_page_infoC

Get detailed information about a specific Wikipedia page including content, summary, and hyperlinked words

Prompts

Interactive templates invoked by user choice

NameDescription
fact_checking_instructionsSystem instructions for automatic Wikipedia fact-checking behavior
fact_check_templateTemplate for structuring fact-checked responses
proactive_verificationInstructions for proactive fact verification without explicit requests

Resources

Contextual data attached and managed by the client

NameDescription
Wikipedia Search Result SchemaJSON schema for Wikipedia search results returned by search_wikipedia_pages tool
Wikipedia Page Info SchemaJSON schema for Wikipedia page information returned by get_wikipedia_page_info tool
Wikipedia Page Summary SchemaJSON schema for Wikipedia page summary returned by get_wikipedia_page_summary tool
Wikipedia Page Sections SchemaJSON schema for Wikipedia page sections returned by get_wikipedia_page_sections tool
Wikipedia Page Sections Info SchemaJSON schema for Wikipedia page sections content returned by get_wikipedia_page_sections_info tool
Wikipedia Language CodesList of supported Wikipedia language codes and their names
Wikipedia API EndpointsDocumentation of Wikipedia API endpoints used by the tools
Wikipedia Tools Usage ExamplesExamples of how to use the Wikipedia tools effectively
Wikipedia Tools Best PracticesGuidelines and best practices for using Wikipedia tools effectively

TDQS

B3.2/5.0

Scored across 5 tools

Disambiguation2/5

Multiple tools have unclear boundaries and overlapping purposes. get_wikipedia_page_info and get_wikipedia_page_summary both provide page information with unclear differentiation beyond 'detailed' vs 'quick summary'. get_wikipedia_page_sections and get_wikipedia_page_sections_info appear to serve nearly identical functions, with descriptions suggesting minimal distinction. This overlap will likely cause agent misselection.

Naming Consistency5/5

All tools follow a perfectly consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform across all five tools, using snake_case and starting with action verbs like 'get' or 'search'. This predictability makes it easy for agents to understand and select tools.

Tool Count4/5

Five tools is a reasonable number for a Wikipedia-focused server, slightly on the lower end but well-scoped. The count feels appropriate for the domain, though it could potentially benefit from additional tools like editing or history functions. Each tool appears to serve a distinct purpose within the limited scope, making the count appropriate.

Completeness3/5

The tool surface covers basic Wikipedia retrieval operations but has notable gaps. While it provides good read capabilities (info, sections, summary, search), there's no coverage for write operations, page history, or user interactions that might be expected in a comprehensive Wikipedia interface. The surface is functional but incomplete for full Wikipedia interaction.

Maintenance

ActivitySlowing
ResponsivenessNo issues