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 Madalena
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states 'Get published reviews' with no additional behavioral context (e.g., read-only nature, pagination, authorization needs). The limit parameter is documented in the schema but not elaborated in the description.
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?
The description is concise with two sentences, front-loading the purpose. However, it could be improved by adding a brief note on ordering or filtering without sacrificing conciseness.
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?
Given the simplicity of the tool (one parameter, no output schema, no annotations), the description is adequate but minimal. It lacks information about ordering, default behavior, and any site-specific context that could help the agent use it effectively.
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 already includes default and max values. The description adds no extra meaning beyond the schema, so 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?
The description clearly states the action ('Get') and the resource ('published reviews'), and specifies the fields returned ('reviewer name, rating, title, and content'). It distinguishes itself from sibling tools by focusing specifically on reviews.
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?
The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The name and description imply it is for fetching reviews, but no when-not or alternative tools are cited.
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/5.0
Disambiguation5/5
Each tool targets a distinct resource or action: search, get, list, create, submit, etc. Potential overlaps like create_booking vs request_reservation vs reserve_event_tickets are clarified by descriptions distinguishing appointment booking, restaurant table requests, and event ticket holds.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with underscores (e.g., list_services, get_place, create_booking). No mixing of styles, and verbs accurately describe the operation.
Tool Count4/5
28 tools is slightly above typical range but well-justified given the breadth of the site (places, events, movies, food, booking, forms, etc.). Each tool serves a clear purpose without feeling bloated.
Completeness4/5
Covers major read and action scenarios for a neighborhood directory. Missing update/delete operations for places and bookings, but those are likely not exposed via this API. Minor gaps like canceling reservations are handled externally.