MoneyTools Transcripts

Free signed one-time upload URL

speech_upload_url

Read-onlyIdempotent

Free: mint a short-lived (15 min), single-use PUT URL for local media. PUT the file via plain HTTP (not MCP), then pass upload_id to speech_transcribe. Size cap matches MaxBytes; rate-limited per client. Not a public file host — bytes are deleted after transcription or expiry.

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

Input Schema

Name	Required	Description
`bytes`	No	Optional declared size hint; must not exceed MaxBytes.
`filename`	No	Optional original filename (metadata only).
`contentType`	No	Optional Content-Type to recommend on PUT (audio/* or video/*).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 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, it discloses the URL lifetime (15 min), single-use semantics, size cap tied to MaxBytes, per-client rate limiting, and the data-retention rule that bytes are deleted after transcription or expiry. These are exactly the operational constraints an agent needs and none are available in the structured fields.

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?

Four compact sentences, front-loaded with the core action, followed by the required next step, the limits, and the retention caveat. No sentence is filler and nothing is buried.

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 URL-minting tool with no output schema, it covers the full lifecycle: what is minted, how to use it outside MCP, which tool consumes the upload_id, and when the bytes disappear. An agent can act correctly without further information.

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 description coverage is 100%, so all three optional parameters are already documented. The description adds only one piece of meaning, that the size cap corresponds to MaxBytes; it does not explain what filename or contentType affect in practice. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'mint a short-lived (15 min), single-use PUT URL for local media.' It immediately establishes what the tool produces and how it differs from the sibling transcription tool, which it names as the consumer of 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?

It states the required workflow explicitly: 'PUT the file via plain HTTP (not MCP), then pass upload_id to speech_transcribe,' and rules out one misuse case ('Not a public file host'). It does not say when an agent should skip upload entirely and call speech_transcribe another way, so it stops short of full when/when-not coverage.

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?