Skip to main content
Glama

Sevana Voice Quality

Upload a small file inline

upload_inline

Upload a WAV or pcap file as base64 in the tool arguments (2 MB at most after decoding). Returns an upload_id for the analysis tools. Larger files: use create_upload.

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": {
      "content_base64": "<content_base64>"
    },
    "name": "upload_inline"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNofile kind: "wav" (default) or "pcap"
filenameNooriginal file name, for display only
content_base64Yesthe whole file, base64 encoded

Output Schema

NameRequiredDescriptionDefault
wavNo
filenameNo
upload_idYes
expires_atYesthe file is deleted at this time
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive write, and the description adds genuinely useful behavior beyond them: the 2 MB decoded size ceiling and the upload_id handoff to analysis tools. It does not mention that repeated calls create separate uploads (consistent with idempotentHint=false) or that uploads persist until delete_upload is called, which are the remaining gaps.

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 short sentences, front-loaded with the format and mechanism, then the size constraint, then the routing to the alternative. No redundant restatement of the title or schema.

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?

A follow-up output schema exists, so the upload_id mention is a bonus rather than a necessity, and the size boundary plus alternative route cover the main decision an agent must make. The only omissions are lifecycle details (persistence, cleanup, duplicate uploads) that would matter for multi-step workflows.

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 kind, filename, and content_base64 are already documented with defaults and display-only semantics in the schema. The description adds only the clarification that the 2 MB limit applies after decoding, which is a modest gain over the structured fields.

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 resource ('Upload a WAV or pcap file as base64 in the tool arguments'), names the accepted formats, the size ceiling, and the return value (upload_id). It is immediately distinguishable from create_upload, the bulk/large-file path.

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?

It gives an explicit selection rule: use this for files up to 2 MB after decoding, and 'Larger files: use create_upload.' Both the when and the when-not, plus the named alternative, are present in the text itself.

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