The failure this fixes
Indian place names collide. Ask for jai and a village called
Jai outranks Jaipur; ask for
jaipur and Bijaipur, Madhya Pradesh is right
behind it. An agent filling a form picks one and moves on. Four minutes of
birth-time error moves the Lagna; several hundred kilometres of birth-place
error moves everything.
The failure is silent. That is what makes it worth a tool rather than a better prompt.
Try it
With WebMCP enabled, ask your agent something like “What is my moon sign? I was born 15 August 1995 at 14:30 in jaipur.” Watch what it does with the place.
Birth place
No birth place resolved yet.
Tools offered right now
Result
No calculation yet.
Agent activity
Every tool call the agent makes on this page, as it happens.
How the tools are shaped
resolve_birth_place- Returns every match with its state and coordinates. When more than one comes back it says, in the tool result itself, that the user has to choose. The tool never picks.
confirm_birth_place- Records the human's answer. Rejects anything that was not among the candidates, and refuses a name that is still ambiguous across states.
calculate_moon_sign,check_mangal_dosh,check_sade_sati-
Real calculations against a live Swiss-Ephemeris backend, gated on a
confirmed place. How that gate is enforced depends on what the browser
implements, and the banner at the top says which one you are getting.
Where
provideContextexists the page republishes the toolset on every state change, so these are not offered at all before confirmation. Chrome shipsregisterToolwithoutprovideContextorunregisterTool, so a page cannot withdraw what it has published — there all five stay registered and these three refuse at call time instead. Same outcome, weaker guarantee.