Namaste America

submit_listing

Submit a new Indian-American business/listing for REVIEW — it does NOT go live automatically.

`vertical` is the category key (restaurants, temples, groceries, professionals, salons, apparel,
sweets, studios, services, community, legal, education, realestate, finance — not events, which are
agent-managed). The submission enters a human moderation queue and is published only after an admin
approves it. `name` is required; provide as much else as you can. Returns {'ok', 'id'} or
{'ok': False, 'error': 'bad_vertical'|'name_required'}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`name`	Yes
`phone`	No
`state`	No
`website`	No
`vertical`	Yes
`address_full`	No
`contact_email`	No

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.

AddedJul 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description must cover behavioral traits. It discloses that the tool is write-only (submits for review) and mentions the return values including error cases. It does not mention side effects, rate limits, or authentication, but the moderation queue context is sufficient.

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 two short paragraphs with the key action and consequence front-loaded. The second paragraph clarifies the vertical and return format. Every sentence adds value without redundancy.

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 8 parameters, no schema descriptions, and no annotations, the description covers the core purpose, the review workflow, vertical categories, required field, and return values. The other optional fields are standard and likely self-explanatory. The output schema is described in the description, making it complete for an agent.

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 coverage is 0%, so the description must compensate. It adds semantics for 'vertical' (list of valid categories) and notes that 'name' is required. However, it does not explain other optional parameters like city, state, phone, etc. The description provides partial but not complete parameter guidance.

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 tool submits a new Indian-American business/listing for review, and it explicitly distinguishes itself from sibling tools like submit_correction and submit_review. The verb 'submit' and resource 'listing' are specific.

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 that the submission goes into a human moderation queue and is not live automatically. It also notes that 'events' are not valid verticals as they are agent-managed, providing a clear when-not-to-use. It could contrast more with submit_correction but the difference is implicit.

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.