Qwen3.8-Omni-Flash for audio agents: tool access
Qwen3.8-Omni-Flash is an omnimodal model for agents. Whatever model you pick, give it Sume's hosted MCP tools and check tools_list before any paid call.

The Qwen release feed for September 17, 2026 lists Qwen3.8-Omni-Flash, described as native omnimodal across audio, vision and text for agentic productivity and creative work. The feed says nothing about Sume. Any agent on any model can use Sume's hosted MCP at https://mcp.sume.com/mcp if its client speaks remote HTTP MCP.
What the release says
Per the Qwen release updates page, read on 2026-10-03, Qwen3.8-Omni-Flash is native omnimodal (audio, vision, text). That is the full extent of what this post asserts about the model. Check Qwen's own documentation for limits, pricing and tool-calling support.
What Sume exposes to an agent
Hosted MCP wraps selected public API capabilities as tools. Paid generation tools include generate_image, generate_video, music_create, tts_create and stt_create. Job tools include jobs_status, jobs_wait and jobs_result. It is not full parity with the HTTP API, so discover the live contract with tools_list and tools_schema.
| Tool | Kind | Note |
|---|---|---|
| stt_create | Paid | Speech to text |
| tts_create | Paid | Text to speech |
| music_create | Paid | Music generation |
| jobs_wait | Read | Wait on one or up to 20 job ids |
| tools_list | Read | Visible tools with safety metadata |
Gates that apply to any model
Paid and write tools require an idempotency_key. dry_run=true previews cost without submitting, and max_spend_usd is enforced only when provided. Under OAuth the default scope is read-only; write and paid tools stay hidden until mcp:write is granted or an API key is used.
{
"idempotency_key": "voiceover-take-001",
"dry_run": true,
"max_spend_usd": 1
}A sensible first run
Connect the client, call mcp_health, then tools_list. Ask the agent to restate which tools it can see before it plans. If the model cannot call tools reliably, keep it on read-only discovery and put a human between it and any paid call.
Sources
Related posts
More in Agents
- script_run or Agent Completion: which for a GPT-6.1 Sol agent?
A GPT-6.1 Sol coding agent can call Sume via MCP script_run or Agent Completions. Which fits fan-out of known calls, and which fits open-ended tasks.
- TikTok trend search then import over Sume MCP: $0.10 + $0.15
Searching TikTok trend metadata costs about $0.10 and importing one video about $0.15 over Sume MCP, so a find-and-mirror step is about $0.25 before generation.
- What did my seller agent spend? Read Sume usage by thread
Amazon's Seller Assistant plugin logs its actions with audit trails. For the media your agent made through Sume, read the cost by thread_id and run_id.
- Who authorizes agent spend on Sume: mcp:write, key and balance
On Sume, spend is authorized by the token: mcp:read hides paid tools, mcp:write allows them, and an API key sees all. There is no mcp:paid scope.
Written by Sume