Skip to main content
Glama

Estimate visual production

estimate_production
Read-onlyIdempotent

Return a directional RUB production range and timeline only when the user explicitly asks about price, cost, budget, quote, or budget fit. This tool is read-only, non-binding, and never collects contact details or submits a brief. Choose WHOLE_PRODUCTION for a finished deliverable and BOUNDED_SHOT_POST for named shots/scenes/post work; use INFERRED when that scope is genuinely ambiguous, or SCENARIO for a clearly labeled hypothetical. For production diagnosis without pricing, use diagnose_production instead.

Input Schema

NameRequiredDescriptionDefault
modeYesROM for an early range; SCOPED_ESTIMATE for a defined scope; BUDGET_FIT to compare scope with a target budget; DEADLINE_FIT to evaluate schedule pressure.
unitsYesProduction line items that drive the estimate. Include every material discipline/unit being priced; each item explains quantity, complexity, locks, continuity, and basis.
scopeTypeYesWHOLE_PRODUCTION prices the complete requested finished deliverable; BOUNDED_SHOT_POST prices only named shots, scenes, VFX, or post tasks.
exclusionsNoWork explicitly outside this estimate, especially live-action, rights, media, extra versions, or unrequested disciplines.
scopeBasisYesOne concise sentence stating exactly what the estimate includes and excludes from the priced object.
versioningNoVersion/adaptation workload beyond the master deliverable; distinguish simple exports from recomposition and new production.
assumptionsNoExplicit factual assumptions used to make the estimate possible; do not invent client facts.
deadlineDaysNoCalendar days available until delivery when known; null or omit when no deadline is supplied.
scopeDecisionYesUSER_EXPLICIT when the requested object is clear; SCENARIO for an explicitly labeled hypothetical; INFERRED only when scope is genuinely ambiguous, in which case no price is returned until clarified.
scopeEvidenceYesShort evidence for the scope choice. For USER_EXPLICIT, copy a brief verbatim phrase from the user's request that identifies the priced object.
runtimeSecondsYesFinal master runtime in seconds when known; null only when genuinely unknown.
targetBudgetMaxNoUpper bound of the user's target budget in RUB for BUDGET_FIT; omit when no target ceiling is supplied.
targetBudgetMinNoLower bound of the user's target budget in RUB for BUDGET_FIT; omit when no budget floor exists.
externalBidItemsNoKnown cost exposures that require third-party bids; these remain outside the automated production range.
includeDepartmentsNoOptional whitelist of departments to include when the requested estimate intentionally covers only selected disciplines.

Output Schema

NameRequiredDescriptionDefault
modeYes
currencyYes
rangeMaxYes
rangeMinYes
budgetFitNo
scopeTypeYes
confidenceYes
exclusionsYes
scopeBasisYes
assumptionsYes
costDriversYes
departmentsYes
scheduleFitNo
scopeDecisionYes
scopeEvidenceYes
runtimeSecondsYes
timelineMaxDaysYes
timelineMinDaysYes
unknownCostExposureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • addedInput schema / properties / assumptions / description
      Added value: +"Explicit factual assumptions used to make the estimate possible; do not invent client facts."
    • addedInput schema / properties / deadlineDays / description
      Added value: +"Calendar days available until delivery when known; null or omit when no deadline is supplied."
    • addedInput schema / properties / exclusions / description
      Added value: +"Work explicitly outside this estimate, especially live-action, rights, media, extra versions, or unrequested disciplines."
    • addedInput schema / properties / externalBidItems / description
      Added value: +"Known cost exposures that require third-party bids; these remain outside the automated production range."
    • addedInput schema / properties / externalBidItems / items / properties / label / description
      Added value: +"External cost item that cannot be responsibly priced by this engine, such as talent, location, licensed music, or live-action vendor work."
    • addedInput schema / properties / externalBidItems / items / properties / reason / description
      Added value: +"Why this cost requires an external quote or remains unknown."
    • addedInput schema / properties / includeDepartments / description
      Added value: +"Optional whitelist of departments to include when the requested estimate intentionally covers only selected disciplines."
    • addedInput schema / properties / mode / description
      Added value: +"ROM for an early range; SCOPED_ESTIMATE for a defined scope; BUDGET_FIT to compare scope with a target budget; DEADLINE_FIT to evaluate schedule pressure."
    • changedInput schema / properties / runtimeSeconds / description
      Previous value: -"Final master runtime in seconds when known. Use null only when runtime is genuinely unknown; for whole-production pricing, runtime is a material pricing input."New value: +"Final master runtime in seconds when known; null only when genuinely unknown."
    • changedInput schema / properties / scopeBasis / description
      Previous value: -"One concise sentence stating exactly what the estimate includes. Never imply a bounded shot/post scope is the price of the whole commercial."New value: +"One concise sentence stating exactly what the estimate includes and excludes from the priced object."
    • changedInput schema / properties / scopeDecision / description
      Previous value: -"USER_EXPLICIT when the user request itself clearly targets either a finished commercial/film/video deliverable or a bounded shot/scene/post task. Literal words like whole/only are not required when the requested object is already clear. SCENARIO is for a clearly labeled hypothetical. INFERRED is only for genuinely ambiguous scope and returns no price until clarified."New value: +"USER_EXPLICIT when the requested object is clear; SCENARIO for an explicitly labeled hypothetical; INFERRED only when scope is genuinely ambiguous, in which case no price is returned until clarified."
    • changedInput schema / properties / scopeEvidence / description
      Previous value: -"For USER_EXPLICIT, copy a short verbatim phrase from the user's request; do not paraphrase, add words, or summarize. The phrase must make the requested object clear: a finished deliverable or a bounded shot/scene/post task. For SCENARIO/INFERRED, briefly state that this is a scenario or inferred interpretation."New value: +"Short evidence for the scope choice. For USER_EXPLICIT, copy a brief verbatim phrase from the user's request that identifies the priced object."
    • changedInput schema / properties / scopeType / description
      Previous value: -"WHOLE_PRODUCTION for the complete production being priced; BOUNDED_SHOT_POST for only named shots/scenes/post tasks. Never silently reinterpret one as the other."New value: +"WHOLE_PRODUCTION prices the complete requested finished deliverable; BOUNDED_SHOT_POST prices only named shots, scenes, VFX, or post tasks."
    • addedInput schema / properties / targetBudgetMax / description
      Added value: +"Upper bound of the user's target budget in RUB for BUDGET_FIT; omit when no target ceiling is supplied."
    • addedInput schema / properties / targetBudgetMin / description
      Added value: +"Lower bound of the user's target budget in RUB for BUDGET_FIT; omit when no budget floor exists."
    • addedInput schema / properties / units / description
      Added value: +"Production line items that drive the estimate. Include every material discipline/unit being priced; each item explains quantity, complexity, locks, continuity, and basis."
    • addedInput schema / properties / units / items / properties / basis / description
      Added value: +"Short factual notes explaining why this unit, quantity, complexity, or lock count was chosen."
    • addedInput schema / properties / units / items / properties / complexity / description
      Added value: +"LOW, MEDIUM, HIGH, or EXTREME execution complexity for this unit."
    • addedInput schema / properties / units / items / properties / department / description
      Added value: +"Department responsible for this unit; use the closest production discipline from the enum."
    • addedInput schema / properties / units / items / properties / hardLocks / description
      Added value: +"Number of exact visual constraints this unit must preserve, such as product geometry, identity, logo, camera, or wardrobe."
    • addedInput schema / properties / units / items / properties / id / description
      Added value: +"Stable short ID for this production unit, such as hero-shots, compositing, or edit."
    • addedInput schema / properties / units / items / properties / quantity / description
      Added value: +"Count of comparable units in this line item. Defaults to 1 when omitted."
    • addedInput schema / properties / units / items / properties / recurringEntities / description
      Added value: +"Count of products, characters, vehicles, or other entities that must stay consistent across multiple outputs."
    • addedInput schema / properties / units / items / properties / reusable / description
      Added value: +"True when the unit creates a reusable asset/system that materially reduces repeated production work."
    • addedInput schema / properties / versioning / description
      Added value: +"Version/adaptation workload beyond the master deliverable; distinguish simple exports from recomposition and new production."
    • addedInput schema / properties / versioning / properties / derivedVersions / description
      Added value: +"Count of low-effort versions derived from the master without new composition or production."
    • addedInput schema / properties / versioning / properties / newProductionUnits / description
      Added value: +"Count of versions that introduce new camera, action, mise-en-scène, shot, or equivalent fresh production."
    • addedInput schema / properties / versioning / properties / recomposedVersions / description
      Added value: +"Count of adaptations that require material reframing, redesign, or recomposition."
  2. Changed18 schema fields changed
    • addedInput schema / properties / assumptions / items / maxLength
      Added value: +1000
    • addedInput schema / properties / assumptions / maxItems
      Added value: +50
    • addedInput schema / properties / exclusions / items / maxLength
      Added value: +1000
    • addedInput schema / properties / exclusions / maxItems
      Added value: +50
    • addedInput schema / properties / externalBidItems / items / properties / label / maxLength
      Added value: +300
    • addedInput schema / properties / externalBidItems / items / properties / reason / maxLength
      Added value: +1000
    • addedInput schema / properties / externalBidItems / maxItems
      Added value: +50
    • addedInput schema / properties / includeDepartments / maxItems
      Added value: +20
    • changedInput schema / properties / runtimeSeconds / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 36000,
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / scopeDecision / description
      Previous value: -"USER_EXPLICIT only when the user explicitly distinguishes full/whole/turnkey production from only/just/bounded shots or post. SCENARIO when calculating a clearly labeled hypothetical. INFERRED when the model had to guess the scope; INFERRED calls return no price and require one clarification question."New value: +"USER_EXPLICIT when the user request itself clearly targets either a finished commercial/film/video deliverable or a bounded shot/scene/post task. Literal words like whole/only are not required when the requested object is already clear. SCENARIO is for a clearly labeled hypothetical. INFERRED is only for genuinely ambiguous scope and returns no price until clarified."
    • changedInput schema / properties / scopeEvidence / description
      Previous value: -"A short verbatim phrase from the user's request that supports USER_EXPLICIT, or a short explanation that this is a labeled SCENARIO/INFERRED interpretation."New value: +"For USER_EXPLICIT, copy a short verbatim phrase from the user's request; do not paraphrase, add words, or summarize. The phrase must make the requested object clear: a finished deliverable or a bounded shot/scene/post task. For SCENARIO/INFERRED, briefly state that this is a scenario or inferred interpretation."
    • changedInput schema / properties / units / items / properties / hardLocks / maximum
      Previous value: -9007199254740991New value: +100
    • changedInput schema / properties / units / items / properties / quantity / maximum
      Previous value: -9007199254740991New value: +1000
    • changedInput schema / properties / units / items / properties / recurringEntities / maximum
      Previous value: -9007199254740991New value: +100
    • addedInput schema / properties / units / maxItems
      Added value: +200
    • changedInput schema / properties / versioning / properties / derivedVersions / maximum
      Previous value: -9007199254740991New value: +1000
    • changedInput schema / properties / versioning / properties / newProductionUnits / maximum
      Previous value: -9007199254740991New value: +1000
    • changedInput schema / properties / versioning / properties / recomposedVersions / maximum
      Previous value: -9007199254740991New value: +1000
  3. Changed12 schema fields changed
    • addedInput schema / properties / runtimeSeconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Final master runtime in seconds when known. Use null only when runtime is genuinely unknown; for whole-production pricing, runtime is a material pricing input."
      +}
    • addedInput schema / properties / scopeBasis
      Added value: +{
      +  "description": "One concise sentence stating exactly what the estimate includes. Never imply a bounded shot/post scope is the price of the whole commercial.",
      +  "maxLength": 600,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / scopeDecision
      Added value: +{
      +  "description": "USER_EXPLICIT only when the user explicitly distinguishes full/whole/turnkey production from only/just/bounded shots or post. SCENARIO when calculating a clearly labeled hypothetical. INFERRED when the model had to guess the scope; INFERRED calls return no price and require one clarification question.",
      +  "enum": [
      +    "USER_EXPLICIT",
      +    "SCENARIO",
      +    "INFERRED"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / scopeEvidence
      Added value: +{
      +  "description": "A short verbatim phrase from the user's request that supports USER_EXPLICIT, or a short explanation that this is a labeled SCENARIO/INFERRED interpretation.",
      +  "maxLength": 300,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / scopeType
      Added value: +{
      +  "description": "WHOLE_PRODUCTION for the complete production being priced; BOUNDED_SHOT_POST for only named shots/scenes/post tasks. Never silently reinterpret one as the other.",
      +  "enum": [
      +    "WHOLE_PRODUCTION",
      +    "BOUNDED_SHOT_POST"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "mode",
      -  "units"
      -]New value: +[
      +  "mode",
      +  "scopeType",
      +  "scopeDecision",
      +  "scopeEvidence",
      +  "runtimeSeconds",
      +  "scopeBasis",
      +  "units"
      +]
    • addedOutput schema / properties / runtimeSeconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / scopeBasis
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / scopeDecision
      Added value: +{
      +  "enum": [
      +    "USER_EXPLICIT",
      +    "SCENARIO",
      +    "INFERRED"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / scopeEvidence
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / scopeType
      Added value: +{
      +  "enum": [
      +    "WHOLE_PRODUCTION",
      +    "BOUNDED_SHOT_POST"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "mode",
      -  "currency",
      -  "confidence",
      -  "rangeMin",
      -  "rangeMax",
      -  "timelineMinDays",
      -  "timelineMaxDays",
      -  "departments",
      -  "costDrivers",
      -  "assumptions",
      -  "exclusions",
      -  "unknownCostExposure"
      -]New value: +[
      +  "mode",
      +  "scopeType",
      +  "scopeDecision",
      +  "scopeEvidence",
      +  "runtimeSeconds",
      +  "scopeBasis",
      +  "currency",
      +  "confidence",
      +  "rangeMin",
      +  "rangeMax",
      +  "timelineMinDays",
      +  "timelineMaxDays",
      +  "departments",
      +  "costDrivers",
      +  "assumptions",
      +  "exclusions",
      +  "unknownCostExposure"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description reinforces this while adding genuinely new context: the estimate is 'non-binding' and 'never collects contact details or submits a brief' (contrasting with the submit_production_brief sibling), and no price is returned when scope is INFERRED. It does not cover rate limits or return format, but the added behavioral framing is substantive.

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?

Four sentences, front-loaded with the gating condition, then scope selection, then the sibling routing. No filler; every sentence carries decision-relevant information.

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

Completeness5/5

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

For a 15-parameter, nested, enum-heavy tool with an output schema, the description supplies the gating rule, mode/scope decision logic, and alternative routing that structured fields cannot express. An agent has everything needed to decide whether and how to call it.

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 detailed enum and property docs, so the schema does the heavy lifting. The description restates the scopeType and scopeDecision semantics that the schema already documents and adds no format or constraint detail beyond it, so the baseline 3 applies.

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 (return a directional RUB production range and timeline), the resource, and the exact gating condition (only when the user asks about price, cost, budget, quote, or budget fit). It explicitly distinguishes itself from the diagnose_production sibling, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (pricing/budget intent only), when-not-to-use (production diagnosis, which routes to diagnose_production), and the decision rule for each scopeType and scopeDecision value (WHOLE_PRODUCTION vs BOUNDED_SHOT_POST, INFERRED only when genuinely ambiguous, SCENARIO for labeled hypotheticals). Nothing is left to inference.

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.