# Tool configuration guides

Choose a tool for the task, prepare its credentials, complete the form, test the connection, and validate an actual invocation. Search tools use provider keys or tokens; other tools manage connections through instances.

| Scenario | Tools |
| --- | --- |
| Public web search | Bocha, Tavily, Brave |
| Repository access and coding assistance | GitHub, Codex |
| Application messages, mail, or events | Feishu, Slack, WeCom, QQ Mail |
| Monitoring and cluster information | Grafana, Kubernetes |

For tools with multiple entries, distinguish message sending from event reception, repository APIs from Webhooks, and applications from mailboxes. See [MCP setup](../add-tools.md) for custom services.

Several instance forms include a name, optional description, and timeout. Use names that distinguish business connections. The default timeout is 30 seconds and the maximum is 300 seconds. Search-credential pages do not have an instance-name field.

(tool-configuration-sources)=

## Scope

These field descriptions follow the Chinese MOI 5.0 guides, based on product pages inspected on September 8, 2026 and the supplied `tool-library.zip` configuration material. Where those sources differed, the product form took precedence. Third-party credential menus may change; use the provider's current console.

These guides explain setup and validation. They do not establish that every third-party account has been integrated. Verify saving, connection tests, actual calls, and event delivery separately.

```{toctree}
:maxdepth: 1
:hidden:

Bocha Search <bocha>
Tavily Search <tavily>
Brave Search <brave>
GitHub <github>
Codex <codex>
Feishu <feishu>
Slack <slack>
Grafana <grafana>
Kubernetes <kubernetes>
QQ Mail <qq-mail>
WeCom <wecom>
```

- [Bocha Search](bocha.md)
- [Tavily Search](tavily.md)
- [Brave Search](brave.md)
- [GitHub](github.md)
- [Codex](codex.md)
- [Feishu](feishu.md)
- [Slack](slack.md)
- [Grafana](grafana.md)
- [Kubernetes](kubernetes.md)
- [QQ Mail](qq-mail.md)
- [WeCom](wecom.md)