Skip to main content
Glama
Sign In
Termux MCP Server

Termux MCP Server

by xlisp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vibrate

Trigger phone vibration for a specified duration, with an option to override silent mode.

Instructions

Vibrate the phone.

Args: duration_ms: Vibration duration in milliseconds (default: 1000) force: Vibrate even in silent mode (default: False)

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

Input Schema

NameRequiredDescriptionDefault
duration_msNo
forceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It mentions the force parameter (vibrate even in silent mode) but lacks details on system permissions, side effects, or whether vibration is blocked by device settings. Minimal transparency.

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?

Extremely concise: one line for purpose plus a parameter list. No redundant text. Purpose is front-loaded. Every word is useful.

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?

Simple tool with no annotations and an output schema not shown. The description covers the basic action and parameters. Lacks return value info, but for a side-effect action, this is acceptable. Could be improved with typical use cases.

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?

Despite 0% schema coverage, the description explains both parameters with defaults and semantics: duration_ms and force (vibrate even in silent mode). This adds value beyond the schema, which only lists names and defaults.

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?

The description clearly states the verb 'Vibrate' and resource 'the phone', which is specific and distinguishes this tool from its many siblings. No ambiguity.

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 on when to use this tool versus alternatives. The description only lists parameters without explaining use cases or conditions (e.g., when vibration is appropriate vs. other feedback methods).

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