Skip to main content
Glama

Quote prepared Playground video shots

playground_video_batch_quote
Read-onlyIdempotent

Read the exact prepared text-to-video shot inputs and total credit ceiling in the requested order. This does not submit or approve jobs. Returns per-node video quotes and the total credit cost.

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": {
      "projectId": "<projectId>",
      "nodeIds": "<nodeIds>"
    },
    "name": "playground_video_batch_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdsYesIDs of the existing canvas nodes to use for this action.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
shotsYes
projectIdYes
maxCreditsYes
expectedRevisionYes

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 declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety bar is low. The description still adds real value by explicitly clarifying that the call neither submits nor approves jobs, and that output is ordered per node with a total credit figure — the key behavioral question for a quoting tool.

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 sentences, front-loaded with the action and immediately followed by the key exclusion and the return shape. No filler; the first sentence is dense but every clause carries 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 an output schema present and full schema coverage, the description need not explain return fields, and it still summarizes them. Combined with annotations and the explicit non-submission constraint, an agent has what it needs to call this correctly; only the routing distinction versus the single-shot quote sibling is missing.

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 100%, so both projectId and nodeIds are already documented. The description contributes only 'in the requested order', hinting that nodeIds order affects the returned sequence, but adds nothing about the 2–12 cardinality constraint or what 'prepared' means for a valid node ID. Baseline 3 applies.

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: reads the prepared text-to-video shot inputs and returns per-node quotes plus total credit cost. The 'batch' nature (multiple nodes, ordered) is conveyed by 'in the requested order', but the sibling playground_video_quote for single shots is never named, so differentiation is implied rather than explicit.

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?

The description gives a clear negative boundary: 'This does not submit or approve jobs,' which tells the agent this is a dry-run pricing step. It does not say when to prefer this over playground_video_quote or workflow_quote, nor does it state prerequisites such as the nodes already being prepared.

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.