GoVisit MCP

List destination places

list_destination_places

Read-only

Browse the place cards displayed on a destination's main page. Apply optional filters to that preview and get up to 20 matches. Coverage depends on which cards the page shows.

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": "list_destination_places"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional published place name or partial name.
`limit`	No	Maximum number of results to return.
`audience`	No	Optional published audience label or code.
`category`	No	Optional published category code.
`pagePath`	Yes	Canonical GoVisit page path supplying this tool's published context; no origin, query or fragment.
`activityType`	No	Optional published activity type.
`neighborhood`	No	Optional published neighborhood.
`accessibility`	No	Optional published accessibility label or code.
`administrativeArea`	No	Optional published administrative area.

Output Schema

Name	Required	Description	Default
`data`	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 declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to restate safety. It adds real behavioral context the annotations don't carry: a hard 20-result ceiling and the caveat that 'Coverage depends on which cards the page shows', warning the agent that results may be partial.

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 action and scope, followed by the filter behavior and the coverage caveat. Every sentence carries information; only the phrase 'to that preview' is slightly redundant with the first sentence.

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 need no explanation, and the schema fully documents all nine parameters. The description covers the essential behavioral traits an agent needs (page-scoped preview, 20-result cap, incomplete coverage) and leaves only sibling routing 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 all nine parameters are already documented in the schema. The description only frames them collectively as optional filters on the preview and mentions the limit cap, adding no per-parameter meaning beyond what is structured. 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?

States a specific verb and resource ('Browse the place cards displayed on a destination's main page') and scopes it to a page-level preview, which separates it from list_category_places or search_places in spirit. It never names an alternative outright, so the differentiation is inferable rather than explicit.

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?

'Apply optional filters to that preview' implies when the tool is appropriate, and the 20-match cap signals it is a preview rather than an exhaustive search. There is no explicit when-not-to-use guidance or pointer to a sibling for full search or other page sections.

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?