Skip to main content
Glama

Metis — Find Tools

find_tools

Search Metis's full tool catalogue by keyword and load matching tools on demand, making them callable and returning their names.

Instructions

Search Metis's full tool catalogue and load the matching tools on demand.

Most Metis tools are kept out of the active set to save context; this finds the
ones you need by keyword (e.g. "zotero sync", "clean dataset", "backup",
"knowledge graph", "transcribe"), makes them callable, and returns their names.
After calling this, call the returned tools directly as normal.

Args:
    query: Keywords describing what you want to do.
    limit: Max tools to return/load (default 8).

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key side effect: it mutates the active tool set by making matched tools callable, and it returns names only. It does not say whether previously loaded tools are replaced or accumulated, nor what happens on a zero-match query — meaningful gaps for a state-mutating tool.

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?

Front-loaded with the core action and scope, then the mechanism, then the follow-up instruction — a sensible order. The Args block partially repeats the schema, but the query examples earn their space; a few lines could still be trimmed without loss.

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?

An output schema exists, so return-value explanation is not required, and the description still notes that names are returned. For a two-parameter discovery tool the coverage is nearly complete; only the ambiguity around active-set replacement and empty results remains.

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 compensate and largely does: 'query' is framed as intent keywords (with concrete examples like 'zotero sync', 'clean dataset'), not tool names, and 'limit' is defined as max tools to return/load with the default restated. It still lacks guidance on keyword breadth or how matching behaves when the query is vague.

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 — searching the full Metis tool catalogue and loading the matching tools — plus the observable effect (tools become callable, names returned). It also explains why it exists (tools kept out of the active set to save context), which no sibling name conveys.

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?

The context sentence 'Most Metis tools are kept out of the active set to save context' plus 'After calling this, call the returned tools directly as normal' gives a clear trigger and follow-up action. However, it never distinguishes itself from the nearby loading/discovery siblings such as load_tool_group, list_tool_groups, or find_viz, so the agent must infer which loader to pick.

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