Skip to main content
Glama

Sevana Voice Quality

Create an upload URL

create_upload

Start uploading a WAV recording (kind "wav") or a packet capture (kind "pcap"). Returns an upload_id and a one-time upload_url; send the file as the body of an HTTP PUT to that URL (for example: curl -T recording.wav '<upload_url>'), then pass the upload_id to an analysis tool. The URL works once and expires after 15 minutes; the file is deleted after an hour. Use upload_inline instead if you can only pass tool arguments.

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

Input Schema

NameRequiredDescriptionDefault
kindNofile kind: "wav" (default) or "pcap" (.pcap/.pcapng)
filenameNooriginal file name, for display only
size_bytesNofile size, if known; larger than the limit is refused at once

Output Schema

NameRequiredDescriptionDefault
methodYes
max_bytesNolargest file accepted (0 = no limit)
upload_idYes
expires_atYesthe URL must be used before this time
upload_urlYesone-time URL: HTTP PUT the file as the request body
max_secondsNolongest WAV accepted (0 = no limit)
curl_exampleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the one-time nature of the URL, the 15-minute expiry, the one-hour file retention, and the exact transport (HTTP PUT with the file as the body, with a curl example). None of that is inferable from readOnlyHint/destructiveHint/idempotentHint=false, and it directly prevents failed calls.

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 sentences, front-loaded with the action and kinds, then the mechanics and constraints, then the alternative. Every clause carries operational information; the curl example is compact and immediately actionable.

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?

An output schema exists, yet the description still names the key return values and explains the lifecycle constraints an agent must respect. For a two-step upload tool, the preconditions, expiry, and hand-off to an analysis tool are all covered with nothing material missing.

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 the schema already documents kind, filename, and size_bytes, including the enum-like values and the size-limit refusal. The description only restates the kinds and adds an example filename; it contributes no new parameter semantics such as a size limit value or pcap extension rules.

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?

States a specific verb and resource ('Start uploading a WAV recording ... or a packet capture') and names the two accepted kinds plus what is returned (upload_id and one-time upload_url). It also differentiates itself from the sibling upload_inline, so an agent can choose between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this when you can perform an HTTP PUT, and 'Use upload_inline instead if you can only pass tool arguments.' It also states the required follow-up step ('then pass the upload_id to an analysis tool'), so the full workflow and the alternative are both spelled out.

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.

Resources