Skip to main content
Glama

Number Counter Animation Maker

create_number_counter_animation
Read-onlyIdempotent

Prefill the Number Counter Animation Maker: a number that counts up or down to any value, on a green screen you can key out. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_number_counter_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color. Default: "#00ff00".
decNoDecimal places shown. Default: "0".
durNoSeconds the count takes. Default: 3.
endNoValue the counter ends at. Default: 1000000.
fpsNoExport frame rate. Default: "30".
preNoText before the number, such as $. Default: "".
resNoExport resolution. Default: "720".
sepNoThousands separator. Default: "comma".
sufNoText after the number, such as %. Default: "".
easeNoHow the count speeds up and slows down. Default: "ease-out".
fontNoFont id of the number. Default: "inter".
holdNoSeconds the final value holds at the end. Default: 1.
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
colorNoColor of the number. Default: "#ffffff".
scaleNoSize of the number relative to the frame. Default: 100.
startNoValue the counter starts at. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, the description discloses the two-step behavior: it returns a link that opens the Tool, and the user must press Export there to download the video. It also adds the practical constraint that upload-based icons and images are unsupported. It does not cover auth, rate limits, or link lifetime, but the important workflow behavior is disclosed.

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?

The description is front-loaded, uses three compact sentences, and covers purpose, return behavior, and a key limitation. There is little wasted wording, though the green-screen phrasing is slightly expansive relative to the core tool behavior.

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 16-parameter tool with no output schema, the description supplies the essential missing context: it returns a link, the user exports externally, all fields are optional, and upload-based assets are unsupported. The main omission is that it does not explain when an agent should prefer this animation maker over related sibling tools.

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%, so all 16 parameters already have documented meanings, defaults, and enums. The description adds only that all options are optional, which the schema already conveys via zero required parameters, and provides no further parameter-specific guidance.

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

Purpose4/5

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

The description names a specific action and artifact: prefill the Number Counter Animation Maker, which creates a number that counts up or down on a keyable green screen. This is clear enough to distinguish it from unrelated animation tools, but it does not explicitly contrast it with close siblings such as a countdown animation.

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

Usage Guidelines3/5

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

It explains the post-prefill workflow (open the returned link, then press Export) and notes that file-upload-dependent icons/images are unsupported. However, it does not state when to choose this tool over the sibling animation makers or give any explicit exclusions beyond that limitation.

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.