mobilerun-mcp

Volume Up

volume_up

Raise music playback volume by a given number of steps on a connected device, letting agents adjust loudness during automation.

Instructions

Raise the music volume by steps.

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

Input Schema

Name	Required	Description	Default
`steps`	No
`device`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Raise the music volume' and does not mention volume limits, device selection behavior, whether it is a media vs system volume change, or any side effects.

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

Conciseness4/5

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

The description is a single, short, front-loaded sentence with no filler or redundancy. It is concise, though somewhat under-specified relative to the tool's parameter set.

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

Completeness2/5

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

The description is too terse to be complete for a tool with no annotations, two parameters with no schema descriptions, and no usage guidance. It omits device selection semantics, volume boundaries, and any interaction with sibling volume controls, leaving an agent with important gaps for correct invocation.

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

Parameters2/5

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

The description adds minimal meaning for the 'steps' parameter by indicating it is the increment amount, but it offers no details on range, units, or behavior when the parameter is omitted. The 'device' parameter is entirely unexplained, and schema description coverage is 0%, so the description does not compensate for that gap.

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 clearly states the action ('Raise') and the target resource ('the music volume'), with the increment amount parameter 'steps'. It is distinguishable from sibling tools like volume_down and mute through the direction of the action, though it does not explicitly name alternatives.

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?

No guidance is provided about when to use this tool versus alternatives such as volume_down, mute, or media_control. There are no conditions, exclusions, or context cues beyond the implicit meaning of the tool name.

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

Deploy Server