Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_tools

Find the right MCP tool for a task by searching names, keywords, or task phrases like "remove filler words" or "blur". Returns matching tools with descriptions and required parameters.

Instructions

Find registered MCP tools by name, keyword, or a supported task phrase.

Returns JSON {success, query, count, tools:[{name, description, required_params}]}. Use to find the right tool for a task without reading every description. Pass query with a term such as blur, resize, subtitle, audio, or trim, or a task such as "remove filler words", "resume render", or "keep face in frame". Exact names rank first. Discovery describes contracts, not installed backend availability.

Args: query: Search term — e.g. "blur", "resize", "subtitle", "audio", "trim".

Input Schema

NameRequiredDescriptionDefault
queryYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.5.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does well: it gives the exact response shape, discloses ranking behavior ('Exact names rank first'), and warns that results describe contracts rather than installed backend availability — a real limitation an agent would otherwise misread. The unexplained 'overwrite' parameter is the one behavioral hole.

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 purpose, then return shape, then usage, then args — good ordering with no filler. Minor redundancy: the example terms 'blur, resize, subtitle, audio, trim' are listed in the body and then again in the Args block.

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 explaining return fields is a bonus rather than a requirement, and the description still does it. For a 2-param discovery tool with no annotations, it covers what to pass and what comes back; only the 'overwrite' parameter and any result-count limits remain unaddressed.

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

Parameters3/5

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

Schema coverage is 50%; the description fully compensates for the undocumented 'query' by giving example terms and phrase forms, which is genuinely beyond the schema. However it never mentions 'overwrite', which is surprising for a search tool and is only described in the schema itself — an agent cannot tell from the description whether search can mutate anything.

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?

Opening sentence states a specific verb and resource ('Find registered MCP tools') plus the three lookup modes (name, keyword, task phrase). Against ~190 siblings that are all concrete media operations, this is unmistakably the meta-discovery tool.

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?

Explicitly tells the agent when to reach for it ('to find the right tool for a task without reading every description') and supplies concrete query patterns, including task phrases like 'remove filler words' and 'resume render'. It does not state when NOT to use it (e.g. when the target tool name is already known), so not a full 5.

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