Booyah Index

Search products

search_products

Read-onlyIdempotent

Search published products, vouchers, experiences, memberships and digital goods sold by verified Booyah stores (distinct from search_places, which finds physical businesses). Read-only discovery: returns titles, integer prices in minor units with currency, availability, seller store, related place context when one exists, and a canonical URL to cite. Never creates orders or payments.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City filter (products can also be online-only with no city)
`limit`	No	Max results, 1-50 (default 10)
`query`	Yes	What to look for, e.g. "google maps playbook", "voucher"
`category`	No	Category filter, e.g. "monitoring", "seo-service"
`currency`	No	Currency code, default THB
`language`	No	Preferred text language (falls back en→any)
`place_id`	No	Booyah place slug — only products from the store attached to this place
`product_type`	No	Restrict to one product type
`max_price_minor`	No	Maximum price in minor units
`min_price_minor`	No	Minimum price in minor units (e.g. 149000 = ฿1,490)

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description reinforces with 'Read-only discovery' and 'Never creates orders or payments.' It adds valuable behavioral context beyond annotations by listing the exact return fields (titles, prices in minor units, availability, seller store, place context, canonical URL) and the scope of 'verified Booyah stores.'

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 three sentences, each earning its place: purpose, return details, and safety note. It is front-loaded with the main verb and resource, avoids redundancy, and is highly scannable.

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?

With 10 parameters and no output schema, the description reasonably lists return fields and scopes the search to published products from verified Booyah stores. It does not mention pagination or response list structure, but the limit parameter and return-field list cover the essential context for a search tool.

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 description coverage is 100%, so all 10 parameters already have descriptions. The description's mention of 'integer prices in minor units' aligns with the price parameter descriptions but does not add new information beyond the schema. It provides no additional guidance on parameter interactions or formats.

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 opens with a specific verb and resource: 'Search published products, vouchers, experiences, memberships and digital goods sold by verified Booyah stores.' It explicitly differentiates from a sibling tool ('distinct from search_places, which finds physical businesses'), making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a clear alternative ('distinct from search_places') and a firm exclusion ('Never creates orders or payments'), telling users when to use this tool for discovery and not for transactions. This explicit when/when-not guidance is exemplary.

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

All Booyah Index 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.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: search_places and search_products handle search across different entity types, get_place/get_product/get_store handle retrieval by identifier, and list_cities provides metadata. There is no overlap or ambiguity between tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: list_, search_, get_. The verbs are semantically appropriate (list for enumeration, search for queries, get for retrieval) and the nouns clearly identify the resource being operated on.

Tool Count5/5

Six tools is well-scoped for a read-only search and retrieval API covering two entity types (places and products) plus supporting metadata (cities and stores). Each tool serves a distinct need, and the count is neither too small to be useful nor too large to manage.

Completeness5/5

The tool set provides complete coverage for the stated purpose of discovery and retrieval: users can list coverage cities, search for places and products, retrieve full records for both, and access store details. The read-only nature is explicit, so there are no missing CRUD operations. The workflow from city to search to retrieve to store is fully supported.

Resources

Need Help?