Skip to main content
Glama

search_community_questions

Search the Namaste America community Q&A — real questions Indians in the USA ask and answer ("Telugu-speaking pediatrician in Plano?", "best sweets for Diwali in Edison?").

Returns published questions matching the query, most-answered first, each with a `slug` you can pass
to get_community_answers. A grounded, community-sourced complement to the listings + knowledge base.
Returns {'count', 'results': [{slug, title, city, state, vertical, answer_count}]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Added

TDQS

A3.8/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 the full burden. It discloses that only published questions are returned, sorted by most-answered first, and includes the return structure. However, it does not mention authentication needs, rate limits, or any destructive actions, which is acceptable for a read-only search tool.

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 a single paragraph with front-loaded examples and purpose. It is efficient and includes only relevant details, though the last sentence about being a complement is somewhat extraneous.

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 the presence of an output schema in the description, it explains the return format (`count`, `results` with fields). It adequately covers what the tool does and returns, though it could mention pagination or sorting details beyond 'most-answered first'.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the JSON schema provides no parameter descriptions. The description mentions 'matching the query' but does not explain the `limit` parameter (default 8) or the nature of the `query` field. It adds minimal meaning beyond the schema.

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 searches community Q&A for Indians in the USA, with specific examples ('Telugu-speaking pediatrician in Plano?', 'best sweets for Diwali in Edison?'). It identifies the resource (community questions) and distinguishes from sibling `get_community_answers` by mentioning slugs.

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 implies usage context by noting it returns most-answered questions and serves as a complement to listings and knowledge base. However, it does not explicitly state when to use this tool versus alternatives like `search_knowledge` or other search tools.

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.