Namaste America

submit_review

Submit a community review (1-5 star rating + optional text) for a listing.

`vertical` is the category key (restaurants, temples, groceries, professionals, salons, apparel,
sweets, studios, services, community, legal, education, realestate, finance) and `listing_id` is
the id returned by that category's get_/search_ tools. Reviews are moderated: clean ones publish
immediately and spam/abusive ones are held for human review. Returns {'ok', 'id', 'status'}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`text`	No
`rating`	Yes
`vertical`	Yes
`listing_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses moderation behavior and return format but omits details like idempotency, error handling, or permission requirements.

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?

The description is concise, front-loaded with the purpose, followed by parameter details, moderation behavior, and return format. Every sentence adds value.

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 no annotations and 5 parameters, the description covers inputs, moderation, and output. It lacks details on error handling and the 'name' parameter, but is otherwise sufficient for a simple submission tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description compensates by explaining vertical (listing categories), listing_id origin, rating range (1-5), and text optionality. However, the 'name' parameter is not described.

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: 'Submit a community review' with a specific verb and resource (review for a listing). It distinguishes from siblings like submit_correction and submit_listing.

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 explains when to use the tool and provides guidance on obtaining listing_id from get_/search_ tools. It does not explicitly list exclusions, but the context is clear from sibling names.

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

All Namaste America tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.