GoVisit MCP

Get destination overview

get_destination_overview

Read-only

Return the published overview for this GoVisit destination. The result includes the long destination description, nullable SEO meta description, and any legacy overview fields, limited to the page's public overview fields and includes freshness metadata from the page snapshot.

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_destination_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.6/5.0

Behavior4/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 genuine context on top by scoping the result to public page fields only, flagging the SEO meta description as nullable, and disclosing that freshness metadata from the page snapshot is included. That tells the agent something about result trustworthiness that neither the annotations nor the input schema convey.

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

Conciseness3/5

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

The first sentence is well front-loaded, but the second is a run-on that repeats "includes" twice ("limited to the page's public overview fields and includes freshness metadata") and stacks nullable/legacy qualifiers. The content is useful but could be tightened into two short clauses.

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 structure, and it correctly focuses on scope (public fields only) and data provenance (snapshot freshness). For a single-parameter read tool with annotations, this is close to complete; only the relationship to sibling overview/section tools is 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% and the single pagePath parameter is already documented with format constraints (no origin, query or fragment), so the baseline is 3. The description adds only the weak linkage that the path identifies "this GoVisit destination", which is largely redundant with the schema text.

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 ("Return the published overview for this GoVisit destination") and enumerates the payload (long description, SEO meta description, legacy fields). It is clearly distinguishable from list_* and search_* siblings by the word "overview", though it never explicitly contrasts itself with get_destination_section, the nearest neighbour.

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: "published overview" and "public overview fields" signal that this is for public page content rather than draft or admin data. There is no statement of when to pick this over get_destination_section or get_place_overview, and no prerequisites or exclusions are given.

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?