Find the parts a repo needs
find_snippetsReturns, word for word, the parts of a tip that meet one concise English repo need. The need is a short phrase: no code, file contents, paths or secrets. With slug, it reads that tip alone. state fit: whole blocks or named checklist sections; menu: the tip fits but no part was selected (get_tip has the whole text); none: no part selected (search_tips lists candidates). Each part carries its source line, the tip URL with a mark that check_installed reads later, and its durability, check age and models and conflicts_with. Missing metadata means unknown.
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": "find_snippets"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| need | Yes | One concise English task, up to 200 characters, e.g. limit unrelated code edits. Omit repo/framework details unless essential. Never code, file contents, paths or secrets. | |
| slug | No | Optional: a tip already chosen, from a search card, to answer for that tip alone. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | Yes | ||
| menu | Yes | ||
| parts | Yes | ||
| state | Yes | ||
| message | Yes |