GoVisit MCP

Get category section

get_category_section

Read-only

Read the overview or places section of a destination category page. Choose places to inspect the inventory preview for that category. 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_category_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.8/5.0

Behavior4/5

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

The annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral fact beyond them: 'Lists contain up to 20 items', which tells the agent about result truncation. It stops short of explaining pagination, cursoring, or what happens if more than 20 items exist.

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, front-loaded sentences with no filler, and the purpose comes before the section guidance. A small ambiguity remains: 'Lists contain up to 20 items' does not specify which lists, though the context implies the returned items.

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?

The tool is simple: two required parameters, one enum, full schema coverage, an output schema, and read-only annotations. The description therefore needs little: it explains what is read, how to choose a section, and the item cap, which is enough to invoke it correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description still earns an upgrade because it gives meaning to the 'places' enum choice as an 'inventory preview for that category', which is content semantics the schema does not supply.

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: 'Read the overview or places section of a destination category page', and it names the two accepted sections. The purpose is clear, but no sibling is named to disambiguate it from look-alikes such as get_category_overview or list_category_places.

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?

'Choose places to inspect the inventory preview for that category' implies which section value to pick and what that value is for, so usage is partially guided. However, it gives no explicit when-not conditions or alternatives, and it does not say when an agent should reach for this tool over the related overview or list tools.

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?