Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

List changes

list_changes
Read-only

Your edits the user hasn't reviewed yet, one entry per step you took, with the clips each one added, removed, moved, trimmed or edited. The editor draws them on the timeline, and the user can keep or undo any step, not only the last. Use it to tell the user what you changed.

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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive, and the description adds useful context: results are per-step, include clip operations, are drawn on the timeline, and can be individually kept or undone. It omits ordering or pagination details, but adds substantial behavioral context beyond the annotations.

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?

Three compact sentences, front-loaded with what is returned, with no filler. The first sentence is dense but still clear and appropriately sized.

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?

For a simple read-only list with one optional parameter and no output schema, the description sufficiently explains the return shape and user actions. A minor gap is that it does not mention ordering or whether all history is included.

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?

The only parameter, projectId, is fully documented in the schema, and the description adds no parameter-specific meaning. With 100% schema coverage, the baseline of 3 is appropriate.

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 the resource precisely: unreviewed edits, one entry per step, with the clips each step added, removed, moved, trimmed, or edited. It does not explicitly name sibling tools like keep_changes or revert_changes, so sibling differentiation is only implied.

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?

Provides a clear use case: 'Use it to tell the user what you changed.' It also notes the user can keep or undo any step, but it does not state when to call this versus keep_changes, revert_changes, or check_edit.

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