Smart Tool Search

StackJack serves tens of thousands of connector tools. Finding the right one by keyword works when you already know what the tool is called, and badly when you describe the job instead. Smart tool search adds a second pass on top of the keyword search: a specialist service reads what you asked for and moves the tools that actually do that job to the top.

It is on by default and it is free. It never draws your credits, and it never uses your own vendor key.

Where it applies

How it reads your request

1. It asks which system the request belongs to. "Reboot the file server" is an RMM job; "raise a ticket" is a PSA job. StackJack offers the connectors you are entitled to and takes at most the two best answers. If you already narrowed the search to one connector, or your organization has only one, this step is skipped — the answer is already known.
2. It builds a candidate pool from the best keyword hits plus every tool you can see on the chosen connectors, capped so a very large connector cannot crowd out everything else. A connector with more tools than the cap contributes its best keyword matches first.
3. It asks, per step you described, which one tool performs it. Your request can carry several steps ("find the client, then list its open tickets, then post a summary") and each is judged on its own. A step no tool fits promotes nothing rather than promoting the least-bad option.
4. It merges the answers and returns the list with the well-matched tools first.

What it does not change

• Your entitlements. Reordering is presentation. A tool you cannot call is never promoted into your results, and a tool your endpoint's selection excludes stays excluded.
• The result shape. Every field the search returned before is still there, with the same meaning. A tool promoted by the second pass but not matched by keyword simply reports no matched phrases.
• Your credits. Never, on any of the three surfaces.

When it does not run

Any of these returns exactly the keyword result you would have had before, with nothing said and nothing charged:

• The service is unreachable, slow, or answers with something StackJack cannot use.
• The whole second pass takes longer than its budget — it is capped at a couple of seconds, so search never becomes the slow part of a conversation.
• Your organization has an EU storage home and has not turned on fast decisions.
• Nothing in the pool is judged a good enough match to promote.

A partial answer is treated as no answer: if any part of the pass fails, the whole reordering is discarded rather than applied to some of your search and not the rest.

Getting better results

• Describe the job, not the tool. "Put the device into maintenance mode for an hour" beats "maintenance".
• Name the system if you know it. That skips the guessing step and spends the whole budget on picking the tool.
• Keep multi-step requests as one sentence per step. Each step is judged separately, so a clear step list gets a clear tool list.
• Assume identifiers are known. The service is told not to promote a search or lookup tool unless finding the record is the whole job, so asking for "the ticket's details" returns the read, not the search.

Related pages

• How Tools Work
• StackJack Platform Tools
• Fast Decisions and Your Own TypeSafe Key