MoneyTools Transcripts

Free upload URL for a long-file job

speech_job_upload_url

Free: mint a signed single-use PUT URL for a long file (up to 100 MB / 180 min; MP3/WAV are segmented). PUT via plain HTTP; the PUT response carries the exact price. Then speech_job_submit with uploadId.

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

Input Schema

Name	Required	Description
`bytes`	No	Optional file size hint in bytes.
`summary`	No	Include a short summary when done.
`webhook`	No	Optional public https URL for a signed job.done callback.
`language`	No	Optional language hint (e.g. en, zh).
`contentType`	No	Content-Type to use on PUT (audio/* or video/*).
`durationSeconds`	No	Declared duration hint (can only raise the price).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: the URL is signed and single-use, the transfer is a plain-HTTP PUT, the exact price is revealed only in the PUT response, and MP3/WAV are segmented. These are non-obvious operational traits an agent cannot get from the annotations or schema, and they are consistent with idempotentHint=false.

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?

Three dense sentences with zero filler, front-loading the free/cost signal and the file-type limits before the follow-up workflow step. Every clause carries decision-relevant information.

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 URL-minting tool with no output schema, it covers limits, cost disclosure, transport, and the next step. It leaves gaps on URL expiry, whether uploadId is returned in the response, and any auth requirements, which matter for an agent orchestrating the upload.

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 all six optional parameters are already documented, including the note that durationSeconds can only raise the price. The description adds only the global 100 MB / 180 min caps that bound bytes and durationSeconds; it does not explain contentType, webhook, summary, or language beyond the schema.

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: 'mint a signed single-use PUT URL for a long file', with concrete scope limits (100 MB / 180 min). It differentiates itself from the short-file sibling implicitly via 'long file' and the size cap, but never names speech_upload_url, so the contrast must be inferred.

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 clear usage context: use this for long files within the stated caps, then immediately follow with speech_job_submit using the returned uploadId. The size/duration limits function as an implicit when-not signal. It stops short of explicitly naming the alternative to use for shorter files or stating any preconditions.

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

All MoneyTools Transcripts tools Inspect

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

Need Help?