MoneyTools Transcripts

Async long-file transcript job (paid)

speech_job_submit

Submit a long audio file (url or uploadId) as an async job: 0.002 USDC per started minute (exact, x402 Base USDC), up to 180 min. Without payment returns PaymentRequired with the exact price; pay via _meta["x402/payment"]. First segment is transcribed before settlement; then poll speech_job_status or get a signed webhook.

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_submit"
  }
}

Input Schema

Name	Required	Description
`url`	No	HTTPS direct media URL you have the right to process (not a platform page).
`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).
`uploadId`	No	job_… id from speech_job_upload_url after the PUT.
`durationSeconds`	No	Declared duration hint (can only raise the price).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses pricing, the 180-minute cap, the PaymentRequired behavior, how payment is supplied via _meta, and that the first segment is transcribed before settlement. This is substantial behavioral context for a paid mutation tool.

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?

The definition is compact and front-loaded: purpose first, then pricing/payment, then post-submit behavior. Every sentence carries useful operational information.

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 an async paid job with no output schema, the description covers the essential flow: submission inputs, exact pricing, payment handshake, duration cap, early transcription behavior, and completion via polling or webhook.

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 parameters already have descriptions. The description reinforces the url-or-uploadId input modes and payment mechanics, but it adds little parameter-level meaning beyond what the schema already provides.

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 gives a specific verb and resource: submit a long audio file as an async job. It also states the paid, long-duration scope, which clearly separates it from short synchronous transcription and from status/upload helpers.

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?

It establishes the context for use: long audio files, async processing, and paid x402 flow. It also names two completion paths, polling speech_job_status or receiving a signed webhook, but it does not explicitly exclude alternatives such as synchronous transcription.

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?