skills.rest
missingbulb
missingbulbCOMMUNITY
Explore all skills by this author →
GitHub

searching-for-a-tool

Guides ToolSearch queries for finding deferred harness tools by name.

Updated Jun 12, 2026
Search Tags:#mcp#tool discovery#tool search#deferred tools#select syntax#harness tools
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill searching-for-a-tool-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: searching-for-a-tool
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/basics/skills/searching-for-a-tool
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill searching-for-a-tool-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a tool search returns nothing, it is easy to wrongly conclude a capability is missing or to waste attempts rephrasing queries. This Skill provides the operational rules for searching deferred tools effectively so you find the right tool before giving up. ## Core Features & Use Cases - Empty-result interpretation: Treats a search with no matches as evidence about the query, prompting query variation before concluding a capability is absent. - Select syntax guidance: Explains that select: accepts short names, qualified names like mcp__github__get_teams, and comma-separated lists to load several tools at once. - Roster exception handling: Identifies when a server's full tool roster is already listed, so one miss there is a definitive answer rather than a reason to rephrase. - Use Case: Before running a ToolSearch for a GitHub integration, load this Skill to learn that select:get_teams and a bare get_teams keyword query both resolve the tool. ## Quick Start Load this Skill before running any ToolSearch query or when a tool search returns no matching tools.

Frequently Asked Questions about searching-for-a-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a deferred tool by name with ToolSearch?▼

Use the select form with either a short name or a qualified name, such as select:get_teams or select:mcp__github__get_teams. A bare short name also works as a keyword query and ranks the exact tool above looser matches.

What does an empty ToolSearch result mean?▼

An empty result is evidence about your query, not proof the capability is absent. Vary the query terms and try the tool before concluding the environment lacks it or telling the user a step is theirs.

Can I load multiple tools at once with ToolSearch?▼

Yes, the select form accepts a comma-separated list of tool names, loading several tools in a single call. This works with both short and qualified names.

When should I stop rephrasing a tool search query?▼

Stop when the server's whole tool roster is already named in the deferred-tools listing. In that one case, a single miss is the definitive answer, so read the roster instead of rephrasing.

When should I use a qualified tool name instead of a short name?▼

Qualify a name when two servers could both carry a tool with the same short name, using the form server__tool. Otherwise a short name resolves readily on its own.

Related Skills

Explore More Software Engineering Skills→
missingbulbmissingbulb

searching-for-a-tool

Guides ToolSearch queries for finding deferred harness tools by name.

Community
Basic
NGTPTENGTPTE

example-command

Parse user-provided arguments and execute the requested action.

Community
Basic
aliciaplsaliciapls

error-troubleshooting

Diagnose Kailash SDK workflow errors and apply documented fixes.

Community
Advanced
orthogonal-shorthogonal-sh
12

find-skill

Search and install skills from the Orthogonal library using the Orthogonal CLI.

Official
Basic