Skip to main content
Glama

find_tool

Read-onlyIdempotent

Discover and inspect the right network API operation by searching with plain-language or exact API queries; review returned details and schemas before invoking read or write actions.

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, uxi, opsramp or specs (the API document lookup).
    Each hit has name, product, summary, kind (read, troubleshoot, config,
    disruptive, firmware, delete or admin) and label (read, diagnostic, write
    or destructive; a show-only check is troubleshoot with label read). Pass include_schema
    to get the arguments a tool takes. Then call invoke_read_tool (kind
    read or troubleshoot) or invoke_tool.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
top_kNo
productNo
include_schemaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds real value beyond that: what each hit contains (name, product, summary, kind, label), the full kind taxonomy, and the show-only-check edge case mapped to troubleshoot/read. It does not mention top_k or result-count limits, which is the main remaining gap.

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 key directive is front-loaded in the first two sentences, and the remaining detail is organized by parameter. The nested taxonomy explanation (kind vs. label, with the show-only-check parenthetical) is slightly dense but each part maps to a real decision the agent must make.

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

Completeness5/5

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

For a four-parameter discovery tool with an output schema present, the description covers what an agent needs: entry-point routing, query formulation, product enumeration, how to expand results with include_schema, and which tool to call next. Nothing essential to a correct first call is missing.

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 burden, and it largely does: query is explained with both a plain-language example and an exact API-call form, product is enumerated in full, and include_schema's effect is stated. Only top_k is left undefined in prose, relying on its schema default of 5.

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?

Specific verb+resource ("Find the tool for a task") with an explicit instruction to call it first, which cleanly separates it from the invoke_* siblings that actually execute tools. An agent can tell instantly that this is the discovery step, not the execution step.

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

Usage Guidelines5/5

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

Explicitly states when to call it ("Call this first") and names the downstream alternatives with the routing condition: invoke_read_tool for kind read or troubleshoot, invoke_tool otherwise. It also explains when to pass include_schema. This is near-complete when/when-not/alternative guidance.

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

Deploy Server

Other Tools