Skip to main content
Glama

Quote Montage

quote_montage
Read-onlyIdempotent

Quote selected clip IDs, or omit clip_ids for every clip still to generate. Show the clips and total credits to the user before generating.

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": "quote_montage"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idsNo
montage_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the default scope when clip_ids is omitted (all clips still to generate) and the expectation that results be surfaced to the user before generation proceeds.

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, both load-bearing, with the default-scope rule front-loaded before the workflow instruction. No filler.

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?

There is no output schema, and the description compensates by indicating the response contains the quoted clips and a total credit figure. For a two-parameter read-only tool this is nearly complete; only the item cap and edge cases are undocumented.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden and does explain the one ambiguous parameter: clip_ids selects specific clips, and omitting it quotes every clip still pending. It does not mention the 10-item cap or clarify montage_id, but the UUID format makes the latter self-evident.

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 (quote) and resource (selected clip IDs within a montage), and the phrase 'before generating' implicitly separates it from generate_montage_clips. It stops short of naming the sibling explicitly, so the distinction relies on inference.

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?

'Show the clips and total credits to the user before generating' clearly places this tool in the workflow ahead of generation, which is actionable guidance. It does not name an alternative tool or state when quoting is unnecessary, so it falls short of 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