Skip to main content
Glama
Sign In

MiOffice — AI-Powered Workspace Studio

by io.github.jsvvsolsllc
OverviewDiscussionsAdmin

mio_audio_speed

Audio Speed — Set a speed from 0.25× to 4×, process your recording, and save an MP3 copy. Learn which speed control changes the exported file.. Video And Audio Studio run — processes in the browser but uses more credits per run than the Document / Image / Scanner workspaces. Welcome credits cover a limited number of runs. Day Pass does not include this workspace. All three credit-based workspaces unlock with the same one-time credit pack — there is no per-workspace subscription. See mioffice.ai/pricing for current plans.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses browser processing, credit consumption, Day Pass exclusion, and that a copy is saved, but it leaves out input requirements, whether the original is preserved, and authentication or file-handling behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence. However, the pricing and workspace paragraph is verbose promotional context, and the sentence about learning which speed control changes the exported file is unclear and does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema or annotations, the description explains the speed range and MP3 output but does not clarify how the recording is supplied or what the result looks like. It is adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description's speed range adds useful domain context even though there are no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: set audio speed from 0.25× to 4× and save an MP3 copy. That distinguishes it from non-audio tools, but it does not explicitly distinguish it from the sibling mio_video_speed, and the phrase 'Learn which speed control changes the exported file' is vague.

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

Usage Guidelines2/5

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

It explains credit and workspace limitations, but gives no guidance on when to choose this tool over alternatives such as mio_video_speed or other audio tools. There are no exclusions, prerequisites, or alternative-selection rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MiOffice — AI-Powered Workspace Studio toolsInspect
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