Skip to main content
Glama

Credits a job will use

estimate_credits
Read-onlyIdempotent

Tells how many Klipa credits a tool will use for a video of a given length, the user's current balance, and whether the job is allowed. On the Free and Plus plans every tool uses credits except the link downloader; Pro and Studio include the tools without AI (compress, convert, cut, resize…) and use credits only for AI tools.

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": {
      "tool": "<tool>",
      "duration_seconds": "<duration_seconds>"
    },
    "name": "estimate_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe Klipa tool to estimate
duration_secondsYesLength of the video in seconds

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?

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuinely new behavior: the tool returns three things (cost, current balance, allowance decision) and credit consumption is plan-dependent and tool-dependent. The notable remaining gap is that it does not say in what unit or structure the answer arrives, but with no output schema that is a minor omission.

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 lead sentence front-loads what the caller gets back, and the second sentence supplies the plan-tier caveat that would otherwise cause misestimation. The mid-sentence enumeration of no-AI tools (compress, convert, cut, resize…) is slightly loose but does real work in clarifying which tools are free on paid plans.

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 two-parameter read-only estimator with full schema coverage and no output schema, the description covers the essentials: what is computed, what accompanies it (balance, allowance), and the plan logic governing the answer. It could go further by naming the moment to call it relative to job creation, but nothing critical for correct invocation is missing.

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 the tool enum and the duration bound (max 86400, exclusive minimum 0) fully documented in the schema. The description only restates that cost depends on duration and tool, adding no format details, units, or rounding behavior beyond the schema. Baseline 3 applies when the schema already carries the parameter burden.

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 uses a concrete verb-plus-resource framing: it names the credit cost, the user's current balance, and an allowance check for a given tool and duration. That is specific enough that an agent can distinguish it from execution siblings like compress_video or create_ai_clips, though it never names a sibling or states explicitly that it is the pre-flight companion to them.

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?

The plan-tier rules (Free/Plus vs Pro/Studio) give real context about when credits get consumed, which implies this tool is worth calling before launching a job. However, there is no explicit instruction such as 'call before create_ai_clips to verify affordability', and no stated exclusion for when estimating is unnecessary.

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