GoVisit MCP

Get category overview

get_category_overview

Read-only

Identify the place category shown on a destination's category page. Read its label, category code, destination identity, and any published count or parent category.

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_category_overview"
  }
}

Input Schema

Name	Required	Description	Default
`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
`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.5/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 without description help. The description adds a little context by implying some returned fields are optional ('any published count or parent category'), but it says nothing about error behavior for a non-category path, resolution of the page path, or caching/permission traits.

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?

Two short sentences, front-loaded with the purpose, with the field list following as supporting detail. Nothing is wasted, though the second sentence is a bare enumeration rather than tightly integrated guidance.

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 an output schema present, the description need not explain return values, and it correctly focuses on what the tool identifies. For a read-only, single-parameter lookup this is nearly complete; only failure modes for a page path that is not a category page are left 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 coverage is 100% for the single pagePath parameter, including length bounds and the 'no origin, query or fragment' constraint, so the schema does the heavy lifting. The description reinforces that the path identifies a destination's category page but adds no new syntax or format guidance beyond the schema, making the baseline 3 correct.

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 names a specific verb and resource ('Identify the place category shown on a destination's category page') and enumerates the fields returned (label, category code, destination identity, count, parent category), which is far more than a restatement of the name. It does not explicitly differentiate itself from near-neighbors such as get_category_section or get_collection_overview, so it stops short of a 5.

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 only implied: the phrase 'on a destination's category page' suggests the agent should call this when already positioned on such a page, but there is no explicit when-to-use, when-not-to-use, or routing to get_category_section / list_category_places. The agent must infer the boundary from sibling names alone, which the framing notes is not sufficient.

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?