GoVisit MCP

Get place section

get_place_section

Read-only

Return one published section for this GoVisit place, including Location spatial details. Arrays are limited to at most 20 items and text values are bounded; the result includes page freshness metadata. The overview section includes owner, chain and operator organization names, each null when unknown; operator identifies the company managing the facility, distinct from profile management.

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_place_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?

The description adds real context beyond the readOnlyHint and openWorldHint annotations: it discloses that arrays are capped at 20 items, text values are bounded, results include page freshness metadata, and overview fields are null when unknown. It also clarifies that operator means the facility-managing company rather than profile management, which is non-obvious semantics.

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?

The purpose is front-loaded and the description is compact, with no redundant material. The middle clauses about array limits, bounded text and freshness metadata are somewhat crammed together, but each sentence carries useful information.

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?

Annotations cover safety and an output schema exists, so the description need not explain return values. The description supplies the important behavioral constraints and overview-field semantics, leaving only explicit sibling routing and pagePath guidance unaddressed.

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%, so the enum and pagePath are already documented. The description adds meaning about the overview section but says nothing about pagePath format or how the other section values behave, so it remains at the baseline for a fully documented schema.

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 states a specific verb and resource: returns one published section of a GoVisit place, with the section chosen by the schema enum. It also identifies what the overview section contains, which helps distinguish this tool from sibling overview tools, though it never names those siblings explicitly.

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?

Usage is implied by the section enum and by the note that the overview section carries owner, chain and operator names, but the description never says when to call this tool instead of get_place_overview or get_place_visit_facts. An agent must infer the routing from section names rather than explicit guidance.

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?