Skip to main content
Glama
Sign In
kinocut

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Describe one operation

describe_operation
Read-onlyIdempotent

Retrieve an operation's full input schema, dispatching family tool, and kino CLI route to inspect exact parameters before invoking it.

Instructions

Return one operation's full inputSchema, the family tool that dispatches it, and its kino CLI route when one exists.

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": {
      "operation": "<operation>"
    },
    "name": "describe_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesRegistry operation name, e.g. video_ai_remove_silence (find names with list_operations).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description's only extra behavioral note is that a kino CLI route is returned conditionally, which is modest value and arguably already visible as an optional field in the output schema.

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

Conciseness5/5

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

One sentence, front-loaded with the primary return value and no filler. Every clause (inputSchema, family tool, CLI route with its caveat) contributes distinct information.

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?

With a rich annotation set, an output schema, and a fully documented single parameter, the definition covers what an agent needs to call it correctly. It could still say what happens with an unknown operation name, but that is a minor gap for a read-only introspection tool.

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 100% and the single parameter is already documented with an example value plus a pointer to list_operations for discovering names. The description adds no format, naming-convention, or error-handling detail beyond that, which is the expected baseline when the schema does the work.

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?

The description states a specific verb and resource ("Return one operation's full inputSchema") and enumerates the payload: schema, dispatching family tool, and CLI route. An agent knows exactly what this tool produces. It stops short of naming siblings (list_operations is only referenced inside the parameter schema), so it is clear but not explicitly differentiated here.

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: the tool is obviously a lookup step whose output feeds a dispatch call, and "when one exists" hints at a fallback path. The description never states when to prefer this over list_operations or over inspecting a family tool directly — that workflow hint lives in the parameter schema, not the description.

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