GoVisit MCP

Get collection section

get_collection_section

Read-only

Inspect part of a named collection. Select overview for the introduction, or places for the entries shown on the collection page. Lists contain up to 20 items.

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>",
      "section": "<section>"
    },
    "name": "get_collection_section"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Published section of the selected page to read.
`pagePath`	Yes	Canonical GoVisit page path supplying this tool's published context; no origin, query or fragment.

Output Schema

Name	Required	Description
`data`	Yes	The requested published section. Overview is an object; lists are arrays of at most 20 items; places/experiences may wrap items in an object; missing opening-hours data is null. Strings and nested lists are bounded by the WebMCP snapshot policy.
`locale`	Yes
`pageId`	Yes
`pageType`	Yes
`freshness`	Yes
`updatedAt`	Yes
`canonicalUrl`	Yes
`completeness`	Yes
`schemaVersion`	Yes
`contentVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral detail not present in structured fields: lists are capped at 20 items, which tells the agent to expect truncated results. It could go further on whether the cap is a hard limit or indicates pagination.

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 short sentences, front-loaded with the core action and then the section choice, with zero filler. The only slight waste is the vague opener 'Inspect part of', which carries little information on its own.

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?

An output schema exists, so return values needn't be explained, and annotations cover safety; parameters are fully described in the schema. The main remaining gap is sibling disambiguation, which matters here given several similarly named collection tools, but overall the definition is sufficient to invoke correctly.

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?

With 100% schema description coverage, the schema already documents both parameters including the enum and the path format constraints. The description adds modest meaning by explaining the content behind 'overview' versus 'places', but says nothing about pagePath semantics, so baseline 3 is appropriate.

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

Purpose4/5

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

The description uses a clear verb ('Inspect') on a defined resource ('part of a named collection') and explains what each section yields ('overview for the introduction, or places for the entries shown on the collection page'). It stops short of distinguishing this tool from near-name siblings such as get_collection_overview or list_collection_places, so an agent must still guess which one to call.

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

Usage Guidelines3/5

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

Guidance is limited to choosing between the two enum values, which is really parameter selection rather than tool selection. There is no statement about when this tool is preferable to get_collection_overview or list_collection_places, and no prerequisites or exclusions are given, so usage is only implied.

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?