Skip to main content
Glama

Voicedex

estimate_cost

Read-onlyIdempotent

Cost in USD for a workload, computed here so no unit conversion is left to the model.

models: keys or loose names (up to 6). characters: text to synthesize (TTS). audio_minutes: audio to
transcribe (STT/STS), or for TTS the minutes of speech to produce (converted with tts_chars_per_minute,
default 900 chars ≈ 150 words/min). Passing an STT and a TTS model with audio_minutes gives a voice-agent
pipeline estimate: STT transcribes all audio_minutes, TTS speaks tts_share of them (e.g. 0.5 if the agent
talks half the time); "total_usd" sums the models (LLM and telephony not included). Uses each model's headline
pay-as-you-go price unless a separate streaming rate applies: mode="streaming" (the default "auto" picks it
whenever an STT/STS model is costed together with a TTS model, i.e. a live voice agent) uses the
provider's published pay-as-you-go streaming rate where there is one; mode="batch" uses the headline
(often pre-recorded) rate. Each line's rate_used says which. Volume discounts, free tiers and plan
prices are not applied.

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

Input Schema

NameRequiredDescriptionDefault
modeNoauto
modelsYes
tts_shareNo
charactersNo
audio_minutesNo
tts_chars_per_minuteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld=false, and the description adds substantial behavioral context on top: LLM and telephony costs are excluded, volume discounts/free tiers/plan prices are not applied, and each output line carries rate_used to reveal which rate was chosen. This is exactly the kind of pricing-boundary disclosure an agent needs to interpret results correctly.

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?

Front-loaded with the one-line purpose, then organized by parameter and by mode behavior; every sentence carries information. It is dense and slightly run-on in the parameter list, but nothing is padding given the tool's complexity.

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?

For a 6-parameter, 0%-schema-coverage calculation tool, the description covers inputs, mode resolution, inclusion/exclusion boundaries, and even names two output fields (total_usd, rate_used). With an output schema present, no further return-value explanation is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so for all six parameters: models (keys or loose names, capped at 6), characters (TTS text), audio_minutes (STT/STS audio or TTS speech minutes, converted via tts_chars_per_minute default 900 ≈ 150 wpm), tts_share (fraction of minutes spoken, e.g. 0.5), and mode (auto/streaming/batch resolution rules). That is meaning well beyond bare schema types and defaults.

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?

States a specific verb and resource: 'Cost in USD for a workload,' with the added rationale that computation happens server-side to avoid model-side unit conversion. It's unambiguous against lookup-style siblings like get_model or compare_models, though it never explicitly names an alternative.

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?

Gives concrete conditional guidance: passing an STT and a TTS model with audio_minutes yields a voice-agent pipeline estimate, and mode="auto" selects streaming 'whenever an STT/STS model is costed together with a TTS model.' It does not state when NOT to use this tool (e.g. for pricing comparisons across models), so no explicit exclusions.

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.