Skip to main content
Glama
Sign In

Tevyon

by ai.tevyon
OverviewDiscussionsAdmin

Price a storyboard

get_storyboard_price
Read-only

What create_storyboard costs in credits for these scenes on this model. Free and starts nothing. Tell the user the price before you start it.

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": {
      "idea": "<idea>",
      "scenes": "<scenes>"
    },
    "name": "get_storyboard_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesThe spot in the user's words: what it is for, who is in it, the look.
lookNoOne line of art direction every frame shares: palette, light, set and one motif that runs through the film. Left out: taken from the idea.
modelNoAn image model from list_models (kind image). nano_banana_pro draws grids and keeps faces best.nano_banana_pro
formatNoThe format of each panel (and of the film made from it).9:16
scenesYesThe panels in order, 4 to 30 seconds together (the Kurzfilm's limits).
optionsNoThe model's own resolution or quality from list_models; left out: its best up to 2K.
referencesNoThe user's own uploads (create_upload, import_image): people, products, logos, app screenshots that look the same in every panel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

'Free and starts nothing' adds meaning beyond readOnlyHint: it tells the agent this call consumes no credits and has no side effects, so it is safe to call repeatedly. It is consistent with readOnlyHint=true and openWorldHint=false, but does not describe what the price response actually contains.

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 short sentences with zero filler, and the core definition (what it costs) is front-loaded ahead of the safety note and the workflow instruction.

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?

There is no output schema, so the description should indicate what the price result looks like (single credit total, per-scene breakdown, per-model comparison). For a 7-parameter nested-schema tool that omission is the main remaining gap; everything else the agent needs is in the schema and annotations.

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 coverage is 100%, so the schema already explains every field including nested scene objects and options. The description only signals that scenes and model drive the price, and says nothing about whether options.resolution/quality or references change the cost, which is the operationally important semantic.

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?

The description states a specific verb ('costs in credits') bound to a specific resource ('create_storyboard') and narrows it to 'these scenes on this model'. That anchors it against the generic get_price and create_storyboard siblings 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?

'Tell the user the price before you start it' gives an explicit workflow position: call this before create_storyboard. It does not name get_price as the alternative for non-storyboard pricing, so the when-not case is left implicit.

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

All Tevyon toolsInspect
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