Skip to main content
Glama

Read Montage

read_montage
Read-onlyIdempotent

Read a saved montage, clip IDs, revision and current quote. Use montage.revision as base_revision for edit_montage.

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": {
      "montage_id": "<montage_id>"
    },
    "name": "read_montage"
  }
}

Input Schema

NameRequiredDescriptionDefault
montage_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds useful behavior detail by naming the returned fields and the revision-chaining purpose, but says nothing about failure behavior (missing/unpublished montage) or access requirements.

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 sentences, zero filler, and the payload description is front-loaded before the downstream-usage hint. Every clause earns its place.

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 one-parameter read tool whose annotations already carry the safety profile, the description covers purpose, output contents, and the chaining contract with edit_montage. What's missing is minor: error behavior and the meaning/format of montage_id.

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 0% for the single montage_id parameter, so the description must compensate. It only implies the argument is a saved montage identifier; the UUID format and any scoping (workspace/ownership) are not mentioned. Some value, but not enough to fully cover the gap.

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 specific verb and resource ('Read a saved montage') and enumerates what comes back: clip IDs, revision, current quote. That is enough to separate it from list_montages and get_montage_run, though neither sibling is named explicitly.

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?

'Use montage.revision as base_revision for edit_montage' tells the agent this read is a prerequisite for the edit flow, which is real routing guidance. It stops short of stating when to prefer it over list_montages or get_montage_run, so it is clear context without full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources