Recommend
recommendOne recommendation for what your user needs, and the next step to start using it, as the site's Operator (/operator) picks it. Pass the need in a sentence you write yourself, e.g. "query Postgres and send email": each need it names gets one pick, why it fits, the next step (the MCP client config to paste when the vendor's docs give one, else its setup guide or docs) and two alternatives; two or more picks also come with a /stack link. Name a product to prefer the listings that mention it; say MCP, CLI, API, browser extension or official to narrow the pick. Picked by fixed matching rules, not a model, so the same need always gets the same answer. A need that matches no task is refused with the closest tasks. Never include names, email addresses or phone numbers.
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": {
"need": "<need>"
},
"name": "recommend"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| need | Yes | What the user needs, in a sentence or two, e.g. "query Postgres and send email" (up to 300 characters are read) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| basis | Yes | How the pick is made | |
| notes | Yes | ||
| answer | Yes | The recommendations in plain sentences, one line per need, ready to tell the user | |
| request | Yes | The need as read | |
| stackUrl | Yes | Two or more picks as a shared stack on the site | |
| unmatched | Yes | Needs with no pick, and the tasks closest to them | |
| operatorUrl | Yes | The same request on the site | |
| recommendations | Yes |