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). |
Filipe Coffee
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It only confirms it's a read operation ('Get', 'Returns') and lists output fields, but omits details like pagination, authentication requirements, or rate limits.
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?
Single sentence, no redundancy. Every word contributes: action, resource, scope, and output fields. Properly front-loaded.
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?
Given one parameter (limit) and no output schema, the description covers the basic functionality. Lacks mention of ordering or pagination but is largely complete for a simple read tool.
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% for the single parameter 'limit', which is well-described in the schema. The description adds no additional meaning beyond what the schema already provides, meeting the baseline of 3.
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 states the action 'Get published reviews' and identifies the resource 'Wix Reviews', also listing returned fields. It is clear but does not explicitly differentiate from sibling tools.
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 or not use this tool versus alternatives. The description is purely functional without context for selection.
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 resource or action (e.g., bookings, events, places, menus, forms), with detailed descriptions that clearly differentiate even similar operations like create_booking vs. reserve_event_tickets. No two tools overlap in purpose.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., create_booking, get_availability, list_events). Verbs are semantically appropriate (create, get, list, search, submit) and predictable.
Tool Count4/5
28 tools is slightly above the typical 3-15 range, but the breadth of the neighborhood directory domain justifies each tool. The count feels dense but not excessive, with no redundant tools.
Completeness5/5
The tool set covers the full lifecycle of a neighborhood directory: place search, restaurant menus, events, movie showtimes, booking, reviews, blog, guides, offers, loyalty, forms, and profiles. Obvious gaps like review creation are absent but likely out of scope.