Skip to main content
Glama

Price a music video revision

price_music_video_revision
Read-onlyIdempotent

What revising each shot of a delivered music video costs, before anything is rewritten For a music video whose revisable_until (get_video) is still ahead. shots: each shot's credits (its rewrite and the shots it makes again, remakes: a shot that the next one carries straight on from makes that one again too); base_credits: the revision's setup, paid once whatever is changed; outro_credits: finishing the video again with another outro and no shot made (create_music_video with refinish). A revision of several shots costs base_credits plus theirs; the exact price is the quote of the revision's plan.

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": {
      "video_id": "<video_id>"
    },
    "name": "price_music_video_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe video id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low, yet the description adds genuine behavior: this is a pre-rewrite estimate, not the final price, and the price grows as base_credits plus each shot's credits. It also discloses the remake ripple effect (a shot the next one continues from is made again). It stops short of describing the actual response shape beyond naming three cost fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded with the cost definition, but it is delivered as one run-on with a missing sentence break ('before anything is rewritten For a music video...') and nested parentheses that make the credit model hard to parse. Every sentence does carry information, so nothing is wasted, but the structure costs readability.

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 no output schema and a single trivial input, the description carries the burden of explaining what comes back, and it does: the three credit components plus the aggregation rule. The main remaining gap is the concrete response format and whether the estimate is cached or recomputed per call.

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?

Only one parameter exists and schema coverage is 100%, so the schema fully documents video_id; the description adds only the qualifying context that it must be a delivered video still inside its revisable window. That is useful framing but not syntax or format information beyond the schema, matching the baseline 3.

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 opening states a specific verb and resource: the cost of revising each shot of a delivered music video, computed before any rewrite happens. It also names the returned cost components (shots, base_credits, outro_credits), which no output schema covers. Sibling differentiation is only indirect, via the aside that 'the exact price is the quote of the revision's plan' pointing at quote_music_video.

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?

A real precondition is given: the video's revisable_until (from get_video) must still be ahead, and the outro path is implicitly tied to create_music_video with refinish. However, the boundary against the sibling quote_music_video is left implicit rather than stated as an explicit when/when-not rule, so the agent must infer which of the two pricing tools to call.

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