casper-network-mcp

find_tool

Read-onlyIdempotent

Locate the right network API operation by task or exact call, inspect its arguments, and choose read-only or full invocation for Central, Mist, or ClearPass.

Instructions

Find the tool for a task. Call this first.

    query: what you want to do, in plain words ("bounce port 7 on the
    closet switch") or an exact API call ("GET /api/v1/sites/{site_id}").
    product: central, mist, clearpass or specs (the API document lookup).
    Each hit has name, product, summary, kind (read, troubleshoot, config,
    disruptive, firmware, delete or admin) and label. Pass include_schema
    to get the arguments a tool takes. Then call invoke_read_tool (kind
    read or troubleshoot) or invoke_tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`top_k`	No
`product`	No
`include_schema`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so safety is covered. The description goes beyond them by describing what a hit contains (name, product, summary, kind with its enumerated categories, label) and that include_schema expands the result with a tool's arguments, which meaningfully shapes how the agent consumes the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the 'call this first' instruction are front-loaded, then parameters, then routing; every sentence carries information. The docstring-style indentation makes it slightly denser to parse than a clean paragraph, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description usefully summarizes hit fields and the include_schema effect, and it covers the full discovery-to-invocation workflow including which sibling to call. Missing only edge details such as behavior on zero hits and the meaning of top_k.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it does for three of four parameters: it explains that query accepts plain language or an exact API path (with examples), and it enumerates the product values (central, mist, clearpass, specs) that appear nowhere in the schema. top_k is left unexplained, which is the only real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find the tool for a task') and distinguishes itself from the sibling invoke_read_tool / invoke_tool pair by being the discovery step that precedes them. An agent can tell immediately that this is the entry point of the tool-selection flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives explicit ordering, and the routing rule (kind read or troubleshoot -> invoke_read_tool, otherwise invoke_tool) tells the agent exactly which sibling to use afterward. It stops short of stating when not to call it (e.g., when the tool name is already known), leaving that to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server