get_reviews
Get published reviews for this site (Wix Reviews). Returns reviewer name, rating, title, and content.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max reviews to return (default 10, max 50). |
Vila Mariana
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It only states return fields; lacks details on read-only nature, authorization, rate limits, or pagination behavior beyond the limit parameter.
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 concise sentences without unnecessary words. Front-loaded purpose and output details. Could be slightly improved by integrating parameter context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with one parameter, description covers basic purpose and output fields. Lacks details on default limit behavior, pagination, or ordering, but sufficient for basic usage.
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 covers the limit parameter 100%. Description adds no additional meaning to the parameter, though it mentions output fields. Baseline score 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?
Description clearly states it retrieves published reviews for the Wix Reviews site, explicitly listing the fields returned (reviewer name, rating, title, content). This is specific and distinguishes it from sibling tools like list_products or list_blog_posts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Does not mention context, prerequisites, or conditions for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool targets a distinct action and resource: booking appointments, restaurant reservations, event tickets, searches, etc. No two tools have overlapping purposes; even similar actions like create_booking and request_reservation are for different domains (appointments vs. restaurant tables).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using lowercase and underscores (e.g., get_availability, list_events, create_booking). There is no mixing of styles like camelCase or inconsistent verbs.
Tool Count4/5
28 tools is above the typical well-scoped range but each tool serves a clear purpose within the comprehensive neighborhood directory domain. The count feels justified, though slightly heavy.
Completeness4/5
The tool set covers most major features of a neighborhood directory: places, events, booking, restaurant menus, reviews, forms, etc. Minor gaps exist, such as no create_review or update operations, but core workflows are complete.