PI Doc MCP
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pi_docsA | Search AVEVA PI System documentation (scoped to docs.aveva.com/category/pi-system). Returns titles, URLs, and excerpts. |
| get_pageB | Fetch the text of a PI System documentation page by URL. |
| list_pi_bundles | List all PI System documentation bundles grouped by product area. |
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 2 tools
The two tools have clearly distinct purposes: search returns a list of relevant pages, while get_page retrieves the full text of a specific page. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: 'search_pi_docs' and 'get_page'. The naming is predictable and clear.
With only two tools, the set is minimal but appropriate for a documentation server focused on search and retrieval. It covers the core operations without being overbearing.
The set provides search and full-text retrieval, which are the primary operations for a documentation server. Missing features like browsing by category or listing all pages are minor gaps that do not critically hinder agents.