Skip to main content
Glama
Sign In
Termux MCP Server

Termux MCP Server

by xlisp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

show_toast

Show a temporary message on your phone screen. Choose between short and long display duration.

Instructions

Show a toast message on the phone screen.

Args: text: Text to show short: True for short display, False for long (default: True)

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": {
      "text": "<text>"
    },
    "name": "show_toast"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
shortNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Show a toast message' without mentioning that toasts are auto-dismissing, non-blocking, or that the duration is controlled by the short parameter. Missing details about side effects or response behavior.

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 very concise (two lines for purpose, two lines for parameters) and front-loaded. However, the docstring format could be more readable in a plain text context.

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?

Despite the existence of an output schema (not provided), the description does not mention return values, failure modes, or prerequisites (e.g., that it works only on a phone screen). The tool is simple but missing contextual hints about when it is effective.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: text is 'Text to show' and short is 'True for short display, False for long'. This adds meaning beyond the schema's type and default.

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 'Show a toast message on the phone screen', but does not explain what a toast is (e.g., a brief non-interactive popup). It distinguishes itself from sibling tools like send_notification by being a toast-specific action.

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 show_toast versus alternatives (e.g., send_notification). The description provides no context about appropriate use cases or when not to use it.

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