Skip to main content
Glama

Estimate synthesis cost

estimate_cost
Read-only

Calculate Telnyx text-to-speech list-price cost from a character count, text, or full [PAUSE n] script before rendering, avoiding API calls for long scripts.

Instructions

Estimates the list-price cost for a character count, a text or a full [PAUSE n] script — without calling the Telnyx API. Use this before rendering long scripts.

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": {
      "voice": "<voice>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText whose length should be priced.
voiceYesVoice id in Provider.Model.VoiceId format, e.g. "Telnyx.Ultra.Clara" or "aws.Polly.Vicki".
scriptNoMarkdown script with [PAUSE n] markers; only the spoken characters are counted.
max_charsNo
charactersNoCharacter count to price. Provide this or "text"/"script".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by stating the estimate is computed "without calling the Telnyx API", i.e. no quota or side effects, and that it reflects list price. It does not say what the returned estimate looks like (currency, units).

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?

Two dense sentences, front-loaded with the core operation, followed by the usage cue. Nothing is wasted and there is no boilerplate.

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, five-parameter estimation tool with no output schema, the description covers purpose and input modes adequately. The remaining gap is the return shape (a numeric cost, currency, per-character breakdown), which an agent must discover by calling it.

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 80%, so the baseline is 3. The description's enumeration of the three input modes reinforces the mutual exclusivity already stated in the schema's "characters" and "script" descriptions, and adds little new syntax or constraint detail of its own.

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 gives a specific verb and resource ("Estimates the list-price cost") and enumerates the three input modes: character count, raw text, and [PAUSE n] script. It also implicitly distinguishes itself from render_script via "without calling the Telnyx API" and "before rendering long scripts", though no sibling is named explicitly.

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?

"Use this before rendering long scripts" gives a clear when-to-use context and implies the alternative (actually rendering). There is no explicit when-not guidance, e.g. that pricing short one-off utterances or comparing voices is unnecessary.

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

Deploy Server

Other Tools