Skip to main content
Glama
Sign In
Termux MCP Server

Termux MCP Server

by xlisp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_volume

Adjust the volume of a specific audio stream (music, ring, alarm, notification, system, or call) to a level between 0 and 15.

Instructions

Set a volume level on the phone.

Args: stream: Volume stream - 'music', 'ring', 'alarm', 'notification', 'system', 'call' volume: Volume level (0-15 typical range, depends on device)

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": {
      "stream": "<stream>",
      "volume": "<volume>"
    },
    "name": "set_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
streamYes
volumeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden but provides only parameter details (stream values, volume range) without explaining behavioral traits like permission requirements, immediate effect, or persistence. The typical range hint adds some value, but overall transparency is limited.

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 concise, with one sentence followed by an Args list. It is front-loaded and efficient, though the Args section is slightly structured but not verbose.

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?

Despite having an output schema (context signal), the description does not mention return values or confirmation of success. For a mutating tool with no annotations, more context about post-action state or error handling would improve completeness.

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

Parameters5/5

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

The schema has 0% description coverage, but the description compensates by enumerating valid stream values and providing a typical volume range. This adds significant meaning beyond the raw schema, making parameter selection clear.

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 (set) and resource (volume level). It implicitly distinguishes from sibling 'get_volume' by using 'set' instead of 'get'. However, the phrase 'on the phone' is somewhat vague but acceptable given the context.

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 on when to use this tool versus alternatives like 'get_volume' or other volume-related tools. No prerequisites, conditions, or exclusions are mentioned, leaving the agent to infer usage context.

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