Skip to main content
Glama
Sign In
kinocut

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List family operations

list_operations
Read-onlyIdempotent

Lists video-editing operation families with member counts and each operation's family, verb, required parameters, and side-effect annotations; filter by query or family.

Instructions

List operations: families with member counts, and each operation's family, verb, required parameters and side-effect annotations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional case-insensitive substring filter over operation names, verbs and summaries.
familyNoRestrict to one family tool name, e.g. video_edit_ops. Omit to list all families.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the shape of what comes back (counts, verb, required params, side-effect annotations), but that overlaps with the existing output schema. It says nothing about ordering or result size for a catalog that could be large.

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?

A single dense sentence that front-loads the verb and resource and then enumerates the return fields. No filler, though the enumeration of return fields is largely redundant with the output schema.

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?

Since an output schema exists, the description need not explain return values, and the annotations carry the safety profile. What remains missing is small: guidance on pairing with describe_operation, and any note on ordering or pagination for a full-catalog listing.

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 description coverage is 100%, so both parameters (query, family) are already documented with defaults and examples, and the baseline is a 3. The description contributes no additional meaning about filtering behavior, matching semantics, or interaction between query and family.

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

Purpose4/5

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

States a concrete verb (list) plus the resources (families and operations) and enumerates what each entry carries: member counts, family, verb, required parameters, side-effect annotations. That is clearly distinguishable from describe_operation, though the description never names that sibling as the detail-oriented alternative.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'List' and by the schema note 'Omit to list all families.' There is no explicit when-to-use statement and no routing to describe_operation when an agent needs full detail on one operation, which is exactly the ambiguity a discovery tool should resolve.

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