openground
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documents_toolA | Search the official documentation knowledge base to answer user questions. Always used this tool when a question might be answered or confirmed from the documentation. First call list_libraries_tool to see what libraries and versions are available, then filter by library_name and version. |
| list_libraries_toolA | Retrieve a dictionary of available documentation libraries/frameworks with their versions. Returns a dictionary mapping library names to lists of available versions. Use this tool to see what documentation is available before performing a search. If the desired library is not in the list, you may prompt the user to add it. Args: search_term: Optional search term to filter library names (case-insensitive). If provided, only libraries whose names contain the search term will be returned. |
| get_full_content_toolA | Retrieve the full content of a document by its URL and version. Use this tool when you need to see the complete content of a page that was returned in search results. The URL and version are provided in the search result's tool hint. |
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 serves a distinct, non-overlapping role: listing available documentation, searching within it, and retrieving full content. There is no ambiguity about which tool to use for a given step in the workflow.
All tools follow a consistent snake_case verb_noun_tool naming pattern (search_documents_tool, list_libraries_tool, get_full_content_tool). This is highly predictable and aids agent selection.
With only 3 tools, the server is tightly scoped to its documentation-searching purpose. Each tool is essential and the count is well within the ideal range for a focused server.
The tool set covers the full lifecycle of documentation interaction: discover available libraries, search for relevant documents, and fetch full content when needed. No obvious gaps or dead ends exist for the intended use case.