Skip to main content
Glama

Quote one Playground video clip

playground_video_quote
Read-onlyIdempotent

Quote a supported text-to-video model for one prepared clip. This is read only and does not submit a job. Returns model pricing and the quoted video settings.

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>",
      "modelId": "<modelId>",
      "duration": "<duration>",
      "aspectRatio": "<aspectRatio>"
    },
    "name": "playground_video_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdYesCanonical model ID returned by model discovery or resolution; preserve the user’s selected model.
durationYesRequested video duration in seconds, supported by the selected model.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
aspectRatioYesOutput width-to-height ratio supported by the selected model, such as 1:1 or 9:16.

Output Schema

NameRequiredDescriptionDefault
creditsYes
modelIdYes
durationYes
modelNameYes
resolutionYes
aspectRatioYes
generateAudioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still earns credit by clarifying the practical consequence — no job is submitted and the call yields pricing plus the quoted settings — which is the distinction an agent actually needs when deciding whether quoting is enough.

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?

Three short sentences, front-loaded with the action, then the safety boundary, then the return content. No filler and no repetition of schema details.

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?

An output schema exists, so return values need not be spelled out, and all four parameters are self-documenting. The one soft spot is the unexplained phrase 'one prepared clip', since no parameter corresponds to a clip — the agent must map it to projectId/modelId/duration/aspectRatio on its own.

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%, with each of the four required parameters documented including the duration bounds and aspect-ratio enum. The description adds nothing about parameter meaning or valid combinations (e.g., duration must be supported by the chosen model), so 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: 'Quote a supported text-to-video model for one prepared clip.' The singular 'one clip' implicitly contrasts with the batch-quote sibling, but it never names that sibling, so differentiation requires inference.

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 useful negative boundary — 'read only and does not submit a job' — which tells the agent this is a pricing step, not a generation step. However, it never states when to pick this over playground_video_batch_quote, playground_image_quote, or playground_workflow_quote, nor any prerequisite such as having a prepared clip or a resolved model.

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.