mirror of
https://github.com/pewdiepie-archdaemon/odysseus.git
synced 2026-10-08 16:02:20 +02:00
1.8 KiB
1.8 KiB
name, description, version, category, tags, status, confidence, source, owner, created
| name | description | version | category | tags | status | confidence | source | owner | created | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| tool-discovery | Discover the smallest capable tool set and confirm argument schemas before acting | 1.0.0 | agent |
|
published | 1.0 | builtin | 2026-08-30T00:00:00Z |
When to Use
Use when a task requires tools whose names, capabilities, or argument shapes are not already clear. This is especially useful when many tools are available or a previous call failed because the wrong tool or parameters were selected.
Procedure
- Translate the request into required capabilities such as reading, searching, editing, executing, browsing, or verifying.
- Search the tool index for those capabilities and inspect the returned tool descriptions and schemas.
- Prefer one direct tool over a chain of indirect tools when it can complete the operation and provide evidence.
- Check required parameters, identifiers, path rules, side effects, and approval requirements before calling the tool.
- Make a small read-only probe when the environment or target is uncertain.
- Execute the selected action, inspect the result, and only broaden the tool search if the result shows a concrete capability gap.
Pitfalls
- Do not guess tool names or argument keys from memory when the index or schema is available.
- Do not load unrelated tool groups into context.
- Do not repeat the same failed call without changing the arguments or strategy.
- Do not use a broad shell or browser workaround when a scoped native tool already owns the operation.
Verification
- The chosen tool directly matches the required capability.
- Required arguments follow the exposed schema.
- The result contains evidence of the requested effect or a specific error that guides the next step.