Skip to main content
Glama

phone_volume

Read or change Android volume for media, ring, notification, alarm, call, or system streams by setting levels, percentages, mute, max, or adjusting up/down; returns all levels and ringer mode.

Instructions

Read or change volume. stream: media (default), ring, notification, alarm, call, system. action: get, up, down, mute, unmute, max, a level number, or a percentage like "40%". Returns every stream level and the ringer mode.

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

Input Schema

NameRequiredDescriptionDefault
showNoshow the volume slider on screen
actionNoget | up | down | mute | unmute | max | <level> | <n>%
streamNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the return payload ("every stream level and the ringer mode") and the default stream, which is genuinely useful given there is no output schema, but it omits whether muting/unmuting affects ringer mode, whether changes persist, and any permission requirements for a state-mutating tool.

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 purpose and scope come first, followed by the stream and action vocabularies and the return note, with no filler. It is telegraphic but dense with useful tokens rather than padded.

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 3-parameter, no-required-argument tool with no output schema, the description covers the essentials: purpose, legal values, default, and return content. It is still incomplete on the show parameter's on-screen slider behavior and on side effects or permission needs for the mutating actions.

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 67%, and the description largely restates the enum lists already present in the schema, though it usefully adds the media default (no default is declared in the schema) and an example percentage format. The third parameter, show, is not mentioned in the description but is documented in the schema, so the baseline of 3 is appropriate.

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?

"Read or change volume" gives a specific verb pair and resource, and the enumeration of streams and actions defines the operational scope precisely. An agent can tell this apart from siblings like phone_brightness or phone_settings without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the value lists: it tells you the default stream is media and the legal action tokens, which guides invocation. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as device permissions or Android version constraints, and no routing to alternatives for related settings.

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