public

Traveller reviews

get_reviews

Read-only

Aggregate rating (1–5) and the newest traveller reviews of Kratons from Zicasso and Google, each attributed to the platform that published it, with a link to read them all. A source that cannot be read is listed as unavailable — never invented.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Newest reviews to return (default 6, max 20)

Output Schema

Name	Required	Description
`note`	Yes
`reviews`	Yes
`sources`	Yes
`bestRating`	Yes
`generatedAt`	Yes
`ratingValue`	Yes	Weighted average over the available sources, 1–5
`reviewCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context: reviews are sourced from two named platforms, each review is attributed, and unavailable sources are reported as unavailable rather than invented. This goes beyond the structured annotations.

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

Conciseness5/5

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

Two sentences deliver the core action, data sources, attribution policy, and fallback behavior with no wasted words. The most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the single parameter is fully documented, and annotations cover the safety profile, the description provides everything needed for correct invocation. It also clarifies data provenance and the never-invent policy.

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 only parameter, limit, is fully documented in the schema. The description does not add extra parameter semantics, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource combination: it aggregates ratings and returns the newest traveller reviews from Zicasso and Google with attribution and a link. It clearly distinguishes itself from sibling tools by focusing on traveller reviews only.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly frames when the tool is relevant: whenever traveller review data from Zicasso or Google is needed. It does not explicitly name alternatives or state when not to use it, but the domain is clear enough that an agent can infer appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All public 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?