Skip to main content
Glama

Estimate the cost of a call

autoshort_estimate_cost
Read-onlyIdempotent

Estimate the credit cost of a paid AutoShort call before running it, checking required balance and daily cap without creating or charging anything. Use it to price a tool call or draft render.

Instructions

Price a paid call BEFORE making it: pass {tool, arguments} — the tool name and the exact arguments you would send (or just {draftId} to price autoshort_render_draft). Returns the most credits it can commit, the balance it needs, whether the balance and this key's daily cap cover it, and when it is charged. Nothing is created or charged. Free.

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": "autoshort_estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoe.g. autoshort_generate_video, autoshort_render_draft, autoshort_ugc_render_batch
draftIdNoShortcut: price autoshort_render_draft for this draft (same as {tool: "autoshort_render_draft", arguments: {draftId}}).
argumentsNoThe arguments you would pass to that tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, so the bar is lower; the description still adds real behavioral context by stating 'Nothing is created or charged. Free.' and enumerating what the response contains (max credits, required balance, cap coverage, charge timing). It doesn't discuss error behavior for invalid tool names, but the added context 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?

Front-loaded with the purpose and the call shape, then the return contents, then the guarantee ('Nothing is created or charged. Free.'). Every clause carries information; no filler or repetition of the title.

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?

There is no output schema, so the description must describe returns — and it does, listing the four pieces of information returned. For a zero-required-parameter estimation tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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 the baseline would be 3, but the description adds meaning beyond the schema by explaining the relationship between parameters: you pass the exact arguments you would send to the target tool, and draftId is equivalent to a specific {tool, arguments} combination.

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 opens with a specific verb and object — 'Price a paid call BEFORE making it' — and names the exact input shape {tool, arguments}. It is clearly distinguishable from siblings like get_credit_balance (which reports balance) because the description frames this as pre-flight pricing of a specific tool invocation.

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?

Timing guidance is explicit ('BEFORE making it') and the draftId shortcut is offered as an alternative path for pricing autoshort_render_draft. It does not explicitly say when not to use this tool (e.g., use get_credit_balance for a bare balance check), so it stops short of full routing guidance.

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