Arckép

estimate_higgsfield_cinema

Read-only

Quote a Higgsfield Cinema Studio 4.0 video (higgsfield-cinema-4) in RUB; nothing is charged.

Same request as create_higgsfield_cinema (webhook_url is accepted and ignored). The price follows the provider's live estimate and depends on duration, resolution, audio and the reference videos you pass.

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": {
      "request": "<request>"
    },
    "name": "estimate_higgsfield_cinema"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Consistent with readOnlyHint=true and reinforces it with "nothing is charged," which is the key behavioral guarantee for an agent. It adds real context beyond the annotation: webhook_url is accepted but ignored, and pricing tracks the provider's live estimate and varies with duration, resolution, audio, and reference videos.

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 tight clauses, front-loaded with the verb, resource, and the no-charge guarantee; the parenthetical about webhook_url is efficient and every sentence carries distinct 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, return values need not be explained, and the description covers the pricing model and the ignored field. Given a large, zero-coverage input schema it could say a bit more about which inputs are irrelevant to price, but an agent has enough to call it correctly.

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% and the payload is a 19-field nested object, so the description must carry weight; it highlights the price-driving parameters (duration, resolution, audio, video_urls) and explains the one parameter with surprising behavior (webhook_url ignored). It doesn't cover prompt, max_cost_rub, or the many stylistic enums, but those are largely self-documenting by name.

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?

States a specific verb ("Quote"), a specific resource (Higgsfield Cinema Studio 4.0 / higgsfield-cinema-4), and the currency (RUB), immediately making clear this is the pricing counterpart to create_higgsfield_cinema.

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?

"nothing is charged" plus "Same request as create_higgsfield_cinema" implies this is the pre-flight pricing check for that creation call, giving clear usage context. It stops short of an explicit "use this before calling create" directive or naming exclusion conditions.

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

All Arckép 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.