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_bundlesA | 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 3 tools
Each tool has a distinct purpose: search returns excerpts, get_page fetches full text by URL, list_bundles enumerates product areas. No overlap.
All tools follow a consistent verb_noun pattern with underscores: search_pi_docs, get_page, list_pi_bundles. No mixed conventions.
3 tools is well-scoped for a documentation server, covering search, retrieval, and browsing without unnecessary extras.
The set covers the core documentation workflow: find pages (search), read content (get_page), and explore structure (list_bundles). No obvious gaps.