Skip to main content
Glama
Sign In
PI Doc MCP

PI Doc MCP

by nurnaufal321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_page

Fetch the text of an AVEVA PI System documentation page by URL to get accurate, live documentation content and avoid AI hallucination on PI-specific topics.

Instructions

Fetch the text of a PI System documentation page by URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesdocs.aveva.com page URL from search_pi_docs
max_charsNoMax characters to return (default 4000, max 12000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description only says 'Fetch the text' without stating read-only nature, potential errors, or side effects. Minimal behavioral insight beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One concise sentence, front-loaded with the verb. No redundant information. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple fetch tool, but lacks details about return format, error handling, and whether the text is plain or formatted. Could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already describes both parameters. The description adds no additional meaning beyond 'by URL'. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Fetch', the resource 'text of a PI System documentation page', and the mechanism 'by URL'. It distinguishes from siblings like search_pi_docs and list_pi_bundles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool or when not to. The schema mentions the URL comes from search_pi_docs, but the description itself lacks context or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools