Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_volume

Adjust Android device volume over ADB by stepping up or down, muting, or setting an exact level; optionally target a specific device.

Instructions

Change the volume: up, down, mute, or set an exact level.

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": {
      "action": "<action>"
    },
    "name": "adb_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNofor action=set
stepsNohow many steps for up/down
actionYes
deviceNoserial, ip[:port] or saved alias; omit to use the default device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and adds little: it doesn't say whether 'mute' is a toggle or an absolute zero, whether changes persist on the device, whether a device must be connected first, or what the call returns. Only the mode list itself is disclosed.

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?

A single tight sentence with the resource and all modes front-loaded. Every word earns its place and nothing is padded.

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?

For a four-parameter, non-nested, output-schema-less tool, the description plus schema covers the essentials: what it does, which modes exist, and what each parameter means. The remaining gap is behavioral (mute toggle semantics, return/confirmation), which is a modest omission.

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 75% and the action enum is documented there, so baseline applies. The description adds slight value by tying 'set' to an exact level, but says nothing about 'steps', 'device' targeting, or defaults beyond what the schema already states.

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?

States a specific verb+resource ('Change the volume') and enumerates the four modes, so the agent knows exactly what operation is performed. It does not name or contrast any sibling, but no sibling tool overlaps with volume control, so confusion risk is low.

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?

The enumerated actions imply the usage contexts (raise, lower, mute, set exact level), but there is no explicit when-to-use versus when-not, no guidance on pairing 'set' with a level versus using 'up'/'down' with steps, and no prerequisites mentioned.

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

Deploy Server

Other Tools