Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

Keep ranges

keep_ranges

Keep only these timeline ranges and remove everything else (ripple). Great for highlight reels.

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": {
      "ranges": "<ranges>"
    },
    "name": "keep_ranges"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangesYes
projectIdNoProject to act on (default: the open one)
rippleTrackIdsNoTracks to cut/ripple (default: all unlocked tracks). Lock a music track to keep it continuous.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The description explicitly says it removes everything outside the given ranges, a destructive edit to the timeline, while annotations declare destructiveHint=false. That is a direct conflict an agent could rely on incorrectly when deciding whether to confirm before calling. Nothing is added about undoability, reversibility, or what happens to locked/unlisted tracks.

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?

Two short sentences, front-loaded with the operation and its scoping effect, followed by a single use case. Nothing is padded or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a timeline-mutating tool with no output schema, the description omits critical operational context: units for the ranges, ripple behavior details beyond the word 'ripple', and whether the result is undoable. Combined with an annotation that understates the destructive effect, an agent is not fully equipped to call this safely.

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

Parameters2/5

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

Schema coverage is 67%: projectId and rippleTrackIds carry their own descriptions (including the music-track locking tip), so the description adds nothing there. The required 'ranges' array has no documented units for start/end (seconds? frames?) in either the schema or the description, leaving the most important parameter ambiguous.

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 gives a specific verb and resource ('Keep only these timeline ranges and remove everything else'), which is meaningfully the inverse of delete_ranges. It stops short of naming or contrasting that sibling, so the agent must infer the distinction from the name alone.

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?

'Great for highlight reels' implies the intended scenario (extracting select segments), but there is no explicit when-not guidance, no mention of delete_ranges as the alternative for removing specified spans, and no stated prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Montik toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources