Namaste America

search_knowledge

Grounded answers from the Namaste America knowledge base — culture, festivals, visa/H-1B, tax, banking, and newcomer/settling-in guides for Indians from India living in the USA.

Returns the top matching passages, each with the source document's title + url so you can cite it.
Optionally scope to a `vertical`. Use this for factual "how/what/when" questions rather than the
listing-search tools. Returns {'count', 'results': [{text, title, url, source_type, vertical}]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`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 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as returning top matching passages with source, and optionally scoped to vertical, which is transparent about behavior. No destructive actions are implied, and output structure is given.

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, well-structured in three sentences: domain, return format and optional scoping, usage guidance, and output schema. Every sentence adds value without waste.

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 3 parameters, no annotations, and presence of an output schema, the description covers purpose, usage, output format, and basic behavior. It could mention error handling or pagination, but is adequate for correct invocation.

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 description must add meaning. It explains 'vertical' for scoping but only implies 'query' and 'limit' through context ('top matching passages'). The output schema description helps, but explicit parameter details are lacking.

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 it provides grounded answers from a knowledge base covering specific domains and returns passages with source links. It explicitly distinguishes itself from sibling listing-search tools, making purpose very clear.

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 explicitly says 'Use this for factual "how/what/when" questions rather than the listing-search tools,' providing clear guidance on when to use. It could mention alternatives like 'ask_community_question' but is sufficient.

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.