Skip to main content
Glama
Sign In

PostPod

by com.postpodai
OverviewDiscussionsAdmin

Estimate script audio

estimate_script_audio
Read-onlyIdempotent

Price a script without creating a job or spending credits. Voices are Nora, Leo, Kristine, Ken, and Marko. Output language defaults to English. The audio has no intro or outro.

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

Input Schema

NameRequiredDescriptionDefault
voiceYesNarrator display name or lowercase id: Nora, Leo, Kristine, Ken, or Marko.
scriptYesThe words to speak.
input_languageNoauto or a language code. Defaults to auto.
output_languageNoLanguage code for the spoken audio. Defaults to English (en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation, so the bar is lower. The description still earns credit by disclosing behaviors the annotations do not: no job is created, no credits are spent, and the resulting audio carries no intro or outro segment. It stops short of describing the shape of the returned estimate.

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?

Four short sentences, front-loaded with the differentiator before the supporting facts, with essentially no filler. The voice enumeration and English default lightly duplicate the schema, which is the only reason it does not score higher.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining what an estimate actually returns (credits, duration, character count, or a cost breakdown), and it only implies 'price.' For a read-only estimator whose entire value is its returned figure, that is a meaningful gap.

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 100%, so every parameter is already documented in the schema, including the voice names and the English default for output_language. The description largely restates those schema facts rather than adding syntax, format, or interaction details, so it holds at the baseline.

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 states a specific verb and object ('Price a script') and distinguishes the tool from its siblings by the essential qualifier 'without creating a job or spending credits,' which immediately separates it from create_script_audio_job. The remaining sentences add the scope details (voice set, English default, no intro/outro) an agent needs to interpret the result.

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?

The phrase 'without creating a job or spending credits' makes the intended context clear: use this to get pricing before committing to a real job. It never names create_script_audio_job explicitly as the alternative for actually producing audio, but the contrast is implicit and strong enough that an agent can choose correctly.

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

All PostPod toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources