Skip to main content
Glama

Show a model and its prices

get_model
Read-onlyIdempotent

Show one MakeViral Create model: the shapes, sizes and lengths it makes, the photos, clips and sounds it takes, special inputs (end frame, multi-shot, elements, motion style), and the price in credits for every size and length. With resolution, durationSec and count it also gives the exact price of that choice, so you can tell the user before create_image or create_video.

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": {
      "model": "<model>"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoOptional, how many to price
modelYesModel id from list_models
resolutionNoOptional, to price one choice: e.g. '2K' (image) or '720p' (video)
clipSecondsNoOptional, seconds of a reference clip (they add to the price)
durationSecNoOptional, video length to price
referencePhotosNoOptional, video reference photos (one model charges for more than 5)

Output Schema

NameRequiredDescriptionDefault
modelYes
quoteNo
pricesYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "nano-banana-pro",
      -  "nano-banana-2-1",
      -  "nano-banana-2",
      -  "gpt-image-2-5",
      -  "seedream-5-pro",
      -  "flux-2-pro",
      -  "z-image",
      -  "seedance-2-5",
      -  "kling-3-pro",
      -  "kling-3-omni",
      -  "veo-3-1-fast",
      -  "wan-3",
      -  "minimax-h3",
      -  "seedance-2",
      -  "veo-3-1-quality",
      -  "veo-3-1-lite",
      -  "seedance-2-fast",
      -  "grok-imagine",
      -  "seedance-2-mini"
      -]New value: +[
      +  "nano-banana-pro",
      +  "nano-banana-2-1",
      +  "nano-banana-2",
      +  "gpt-image-2-6",
      +  "gpt-image-2-5",
      +  "seedream-5-5",
      +  "seedream-5-pro",
      +  "flux-2-pro",
      +  "z-image",
      +  "seedance-2-5",
      +  "kling-3-pro",
      +  "kling-3-omni",
      +  "veo-3-1-fast",
      +  "wan-3",
      +  "minimax-h3",
      +  "seedance-2",
      +  "veo-3-1-quality",
      +  "veo-3-1-lite",
      +  "seedance-2-fast",
      +  "grok-imagine",
      +  "seedance-2-mini"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, closed read, so the description's job is to add context — and it does: it discloses that the response contains a full price table per size and length, and that supplying resolution/durationSec/count narrows that to an exact quote. It does not mention error behavior for unsupported combinations, but the output schema covers the return shape.

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

Conciseness4/5

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

Front-loaded with the core action, then a single dense enumeration of what is returned, ending with the pricing-precision payoff and the downstream tools. The parenthetical list of special inputs is slightly heavy but each item carries 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?

For a read-only lookup with a full output schema and fully documented parameters, the description supplies what the structured fields cannot: the breadth of returned model detail and the fact that optional params unlock an exact quote. Minor gap only in not stating how invalid model/option combinations behave.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: it explains that resolution, durationSec and count act together to produce the exact price, which the per-field schema text does not convey. It leaves the pricing effect of clipSeconds and referencePhotos to the schema.

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 and resource ('Show one MakeViral Create model') and then enumerates exactly what is shown: shapes, sizes, lengths, accepted inputs, special inputs, and credit prices per size/length. The word 'one' distinguishes it from the sibling list_models without ambiguity.

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?

Explicitly frames the use case: price a choice so the agent can tell the user before calling create_image or create_video. That is clear when-to-use guidance tied to named siblings, though it gives no explicit when-not conditions (e.g. that list_models should be used first to discover ids, which only appears in the schema).

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