Ask a question in words
ask_questionUse this for a buying question in plain words ("laptop under 1.5 kg with 16 GB RAM", "CRM with SOC 2 and EU data residency"). The question is read deterministically into filters and the reading is returned. It is the SAME evaluation as the website and /api/v1/ask. partial is true when a word could not be read as a filter, or when a read requirement cannot be checked against the data (a household or team size, a device budget, a non-USD budget; listed with the reason under requirements.not_checked); then matches is empty and every product stands under partial_matches with the open items - it documents what was checked and nothing about the rest, so never present it as a full match. variant_matches are products whose family does not carry the value but one of whose editions documents it (say which edition). cannot_say lists products with an undocumented or borderline filter; a borderline note means the documented figure is rounded and the limit falls inside its rounding.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"question": "<question>"
},
"name": "ask_question"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| without | No | Attribute keys of read requirements to set aside, e.g. ["ram_gb"]. They stay listed under requirements.removed and are not checked. Same as ?without= on the website. | |
| question | Yes | The question in words, up to 300 characters. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| read | Yes | ||
| matches | Yes | ||
| partial | Yes | ||
| web_url | Yes | ||
| contract | Yes | ||
| question | Yes | ||
| cannot_say | Yes | ||
| considered | Yes | ||
| requirements | Yes | ||
| not_understood | Yes | ||
| partial_matches | Yes | ||
| variant_matches | Yes | ||
| category_candidates | Yes |