GoVisit MCP

Read documentation page

get_documentation_page

Read-only

Read the current page's published title, headings and structured content, or one section selected by its heading anchor. Returns the canonical URL and explicit truncation information. Reads only the current rendered page; does not fetch other articles.

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": {
      "pagePath": "<pagePath>"
    },
    "name": "get_documentation_page"
  }
}

Input Schema

Name	Required	Description	Default
`section`	No	Optional heading anchor identifying one published section.
`pagePath`	Yes	Canonical GoVisit page path supplying this tool's published context; no origin, query or fragment.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing return characteristics (canonical URL, explicit truncation information) and the no-cross-page-fetch constraint, but says nothing about permission/auth needs or what happens when the requested section anchor is not found.

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

Conciseness4/5

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

Three tight sentences with the scope constraint front-loaded and no filler. Slightly dense packing of return behavior and scope into one sentence, but nothing is wasted.

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?

With annotations, a full-schema and an output schema, an agent has everything needed to invoke it correctly; the description correctly avoids restating return values beyond the truncation warning. Only a pointer to the right sibling for other pages is missing.

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 both parameters are already documented with constraints and examples; baseline 3 applies. The description's 'one section selected by its heading anchor' and 'current page's' phrasing reinforces what section and pagePath mean but adds no format or edge-case detail beyond the schema.

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?

States a specific verb (Read) plus the exact resource (title, headings, structured content of the current page, or one anchored section), and scopes it with 'Reads only the current rendered page; does not fetch other articles.' That negative scope lets an agent separate it from search/other-article siblings without opening a schema.

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

Usage Guidelines4/5

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

Gives clear when-to-use context (current rendered page) and an explicit when-not (does not fetch other articles), which is the main misuse risk. It stops short of naming an alternative such as search_documentation for other pages, so routing is inferred rather than prescribed.

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

All GoVisit MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?