Namaste America

get_offers

Live offers & announcements posted by Indian-American business owners (e.g. "20% off thalis this week", "new weekend Garba class"), optionally filtered by city/state/vertical.

Returns current, non-expired owner posts with the listing they belong to. Great for "any deals near
me this week". Returns {'count', 'results': [{title, body, kind, vertical, listing_id, name, city,
state, created_at, expires_at}]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`limit`	No
`state`	No
`vertical`	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 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, but the description explains that it returns current non-expired posts and includes the output shape. This provides reasonable transparency for a read-only, filtered query.

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 with three efficient sentences: purpose, return shape, and usage example. It is well-structured and front-loaded with the key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the optional parameters and provided output schema, the description is complete. It covers the tool's behavior, filtering capability, and return format, enabling confident agent 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 coverage is 0%, but the description mentions optional filters by city/state/vertical, partially compensating. However, it does not explain the 'limit' parameter or provide additional syntax guidance beyond the schema defaults.

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 retrieves current, non-expired offers and announcements from Indian-American business owners, with optional filters. It specifies the resource ('offers') and distinguishes from siblings by targeting promotional content.

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 includes a concrete example ('any deals near me this week') and implies use for offers only. It does not explicitly state when to avoid this tool, but the context is clear enough.

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.