ai.babysensemonitors.com
Babysense
First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com
Answer 6 · Act 7 · Transact 3 · Score: Not yet scored
Tool inspector
set_visitor_context
Tell this brand a standing preference or constraint the visitor has stated — their size, fit, colour preference, budget. Pass context as {name: value} using the names get_visitor_context reports, e.g. {"Size": "8"}. Use it ONLY for what the visitor actually said about themselves, never for a guess or for a one-off request — a request goes to send_message. The brand decides which of these it recognises and how long it keeps them; this states the preference, it does not store it. Values are short strings.
Input schema
| Property | Type | Required | Description |
|---|---|---|---|
context |
object | yes | Stated preferences as {name: value}, e.g. {"Size": "8", "Budget": "150"} |
Raw JSON schema
{
"type": "object",
"properties": {
"context": {
"type": "object",
"description": "Stated preferences as {name: value}, e.g. {\"Size\": \"8\", \"Budget\": \"150\"}",
"additionalProperties": {
"type": "string"
}
}
},
"required": [
"context"
]
}
Similar websites
cleardose-webmcp-demo.netlify.app
See the ClearDose WebMCP use case, shared Vue and Pinia architecture, demo workflow, source repository, and submission readiness.
4over4.com
4OVER4.COM prints 1,000+ custom products on 60+ paper stocks in Queens, with same-day shipping on most orders and 150,000+ businesses served since 1999.
camdentools.com
Construction tools and equipment
autolab.run
Super intelligence for car lovers. A WebMCP vehicle configurator, an agentic owner's guide with a live digital twin, and the 3D creation engine that measures th…