Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Find Tools

find_tools

Searches Metis's tool catalogue by keyword and loads matching tools on demand, making them callable so you can use the right tools without filling context.

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. "dhis2 tracker", "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).

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries burden. States that tools are made callable and returns names, but does not disclose if it adds to or replaces existing active tools, or any side effects.

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

Conciseness3/5

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

The description is mostly concise but includes an 'Args' section that duplicates schema information. The main action is front-loaded, but the redundancy reduces conciseness.

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?

Covers the tool's purpose, usage, and parameters. Output schema exists so return values need not be detailed. Explains why tools are kept out of active set. Missing details on persistence of loaded tools.

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?

Description adds meaning beyond schema: defines query as 'keywords describing what you want to do' and limit as 'max tools to return/load'. Schema had no descriptions, so this is helpful. Could be more specific about query format.

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?

The description clearly states the tool searches the full tool catalogue and loads matching tools on demand, which is a unique purpose distinct from sibling tools. It provides specific examples of query keywords.

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?

Explains when to use: to find tools by keyword to save context. It tells the agent to call returned tools directly. Does not explicitly state when not to use, but context is clear.

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