Skip to main content
Glama
Sign In
PI Doc MCP

PI Doc MCP

by nurnaufal321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_pi_docs

Search AVEVA PI System docs to get relevant titles, URLs, and excerpts. Optionally restrict to a specific bundle.

Instructions

Search AVEVA PI System documentation (scoped to docs.aveva.com/category/pi-system). Returns titles, URLs, and excerpts.

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": {
      "query": "<query>"
    },
    "name": "search_pi_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms, e.g. 'Kerberos authentication' or 'configure PI Interface buffering'
bundleNoOptional bundle ID to restrict search, e.g. 'pi-web-api', 'af-sdk', 'pi-server-f'
n_resultsNoResults to return (default 5, max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool returns titles, URLs, and excerpts, which implies read-only behavior. However, it does not mention authentication requirements, rate limits, or any other operational constraints. The scope information is helpful, but more detail on behavioral traits would be beneficial.

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?

A single sentence that front-loads the purpose and includes key details (scope, return types). Every word serves a purpose, with no redundancy or fluff.

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

Completeness4/5

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

For a search tool with 3 parameters and no output schema, the description covers the core functionality and return structure. It does not mention pagination or result ordering, but the n_results parameter handles some of that. The sibling tools are not addressed, but the description is sufficiently complete for an agent to understand the tool's primary use.

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 description coverage is 100%, with each parameter having a description in the schema. The tool description does not add extra semantic information beyond what the schema already provides. Baseline score of 3 is appropriate when the schema does the heavy lifting.

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 'Search', the resource 'AVEVA PI System documentation', and the scope ('scoped to docs.aveva.com/category/pi-system'). It also lists the return fields (titles, URLs, excerpts), which distinguishes it from sibling tools like get_page (likely fetches a specific page) and list_pi_bundles (lists 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?

The description implies the tool is used for searching documentation, but provides no explicit guidance on when to use this tool versus alternatives (get_page, list_pi_bundles). There are no 'when to use', 'when not to use', or 'see also' statements, leaving the agent to infer from the name alone.

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