DivineAI

Pujas you can book

search_pujas

Read-onlyIdempotent

DharmikVibes' bookable pujas that are listed right now: title, temple, place, open dates, time slots, languages, and the dharmikvibes.com page where it is booked. The price appears only as listed on the website; this tool never works one out. It books nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_pujas"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Most pujas to return, 1 to 20.
`query`	No	Words from the puja name, temple or place, in English or Hindi, for example Vindhyachal, Bhairav, Kashi.
`on_or_after`	No	ISO date. Only pujas with an open date on or after it.

Output Schema

Name	Required	Description	Default
`note`	Yes
`count`	Yes
`pujas`	Yes
`note_hi`	Yes
`website_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words elsewhere: it discloses that only currently listed pujas are returned, that prices are taken verbatim from the website rather than computed, and that no booking occurs. That is genuine added context beyond the annotations, though nothing is said about result ordering or how many of the available listings a query returns.

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?

Three short sentences, no filler. The what-you-get list comes first, the price caveat and the no-booking disclaimer follow, and every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return shape is already covered, and the description still gives a useful field summary. Combined with fully documented parameters and complete annotations, an agent has everything needed to call this correctly, and the price/booking caveats close the remaining ambiguity.

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 100%, with each of limit, query, and on_or_after already documented including examples and ranges. The description adds no parameter-level detail beyond the returned-field list, so the baseline 3 for a fully described schema applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource ('bookable pujas that are listed right now') and enumerates the returned fields (title, temple, place, dates, slots, languages, booking page). It is clearly a search over puja listings, but it never contrasts itself with the closest sibling, search_darshan, so an agent must infer the split between puja and darshan searches.

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

Usage Guidelines3/5

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

'that are listed right now' implies a currency constraint on results, and 'this tool never works one out' / 'It books nothing' implicitly fences off pricing and booking. However, there is no explicit statement of when to pick this over search_darshan or the guide tools, so the usage boundary is only implied.

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

All DivineAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?