GoVisit MCP

List collection places

list_collection_places

Read-only

Find entries in a named destination collection using its collection page path. Optional filters narrow the existing selection by published card details. Returns up to 20 matches.

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_collection_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.5/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that filters operate on already-published card details and that results are capped at 20 matches, but it does not say how to obtain the required page path, whether results are ordered, or what happens when the cap is hit.

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 identity of the resource and its key, then filters, then the result cap. Little waste, though the repeated 'published' phrasing and the result-cap sentence partly restate the schema's maximum of 20.

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 not be explained, and annotations cover the safety profile. The remaining gap is that the required pagePath is described circularly ('using its collection page path') without saying how an agent should acquire it, which matters for a tool that cannot be called without it.

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%, so every one of the nine parameters is already documented, which sets the baseline at 3. The description contributes only the framing that filters are conjunctive narrowing over published card details and that 20 is a hard ceiling; it adds no per-filter meaning beyond the 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?

States a specific verb and resource: find entries in a named destination collection, keyed on its collection page path. That clearly separates it from get_collection_overview / get_collection_section and from the destination/category listing siblings, though it never names any of them 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 rather than stated: you need a collection page path and optional filters narrow the set. There is no explicit when-to-use vs. list_destination_places, list_category_places, list_related_places, or search_places, and no statement about when filters are inappropriate.

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?