RYLA

ryla_video_swap_cost

Quote the credit cost of a video swap before starting it (no charge). Same price the start tool charges for the same inputs; the charge uses the server-measured clip length.

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": {
      "durationSeconds": "<durationSeconds>"
    },
    "name": "ryla_video_swap_cost"
  }
}

Input Schema

Name	Required	Description
`mode`	No
`resolution`	No
`contentClass`	No	unrestricted for an Unrestricted Fan Content character
`outfitEnabled`	No
`durationSeconds`	Yes	Clip length in seconds
`backgroundEnabled`	No
`seedanceResolution`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does disclose two important behaviors: the call is free ('no charge') and the actual charge uses the server-measured clip length, warning the agent that a quote based on a supplied durationSeconds may not match the final debit. It does not cover error behavior, auth requirements, or whether quotes expire.

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, front-loaded with the purpose and the free-of-charge guarantee, with no filler. Every clause adds information an agent would otherwise have to infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, low-coverage, no-output-schema tool, the description establishes the return value (a credit cost) and its cost-free nature but leaves the pricing model opaque. An agent cannot tell which parameter combinations matter or whether the quote includes a breakdown.

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

Parameters2/5

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

Schema coverage is only 29% across 7 parameters, so the description should compensate but largely does not. 'Same price the start tool charges for the same inputs' hints that parameters must mirror the start call, yet it never explains which inputs drive cost (resolution, mode, outfitEnabled, backgroundEnabled) or how they interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: quote the credit cost of a video swap. It also implicitly distinguishes itself from the sibling that actually starts the job (ryla_generate_video_swap) by describing itself as the pre-flight quote and noting it charges nothing.

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?

The phrase 'before starting it' gives a clear trigger condition and points at the start tool as the alternative action. It stops short of explicit when-not guidance, such as whether to skip the quote if the cost is already known or cached.

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

All RYLA tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?