find_tool
Find the right tool for any network action: search by query (e.g., 'create a VLAN') using semantic and keyword matching, then use the returned name to invoke read or write tools.
Instructions
Find tools by query. Combines semantic search + tool-name keyword match.
Call this first when you need an action. The returned name is what you
pass to invoke_read_tool for read-only tools or invoke_tool for writes.
Results are deduplicated; semantic matches are annotated match='semantic',
name-overlap matches match='keyword', and safety flags mirror backend
ToolAnnotations. Results are compact by default; set include_schema=True
only when you need the full JSON schema for a selected tool. Optional
platform, server, normalized capability, curated/generated origin, and
exact OpenAPI operation-ID filters apply to both keyword and semantic
matches.
Args: query: What you want to do. e.g. "create a VLAN", "disconnect a client". top_k: 1-10 results (default 5). include_schema: Include full JSON schemas in results. Defaults to False to keep MCP responses compact. platform: Filter by normalized platform, such as central, glp, mist, clearpass, or apstra. server: Filter by exact backend server name, such as aruba-monitoring. capability: Filter by read, diagnostic, write, or destructive. origin: Filter by curated or generated implementation. operation_id: Filter by an exact generated OpenAPI operationId.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| top_k | No | ||
| origin | No | ||
| server | No | ||
| platform | No | ||
| capability | No | ||
| operation_id | No | ||
| include_schema | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |