Skip to main content
Glama

app_dismiss_keyboard

Hides the on-screen keyboard so it no longer blocks app content during screen recording or interaction.

Instructions

Hide the on-screen keyboard.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full behavioral burden, and "hide" does convey the essential state change. It does not disclose whether the call is idempotent when no keyboard is shown, whether it returns a success/failure indication, or whether it affects focus on the current text field.

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 front-loaded sentence with no filler or redundancy. Nothing in it could be removed without losing the stated purpose.

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 zero-parameter, no-output UI action the description states the whole operation, which is close to sufficient. It stops short of covering edge-case behavior (no keyboard present, return value, interaction with other app_* UI actions) that an agent would want before invoking it blindly.

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?

The input schema declares zero parameters, so there is nothing for the description to clarify beyond the action itself. Baseline 4 applies for a parameterless tool.

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?

"Hide the on-screen keyboard" names a specific verb (hide) and a specific resource (the on-screen keyboard), so the action is unambiguous. It does not need to differentiate against the listed siblings, none of which appear keyboard-related, but it also offers no explicit contrast to them.

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 condition for use is only implied: an agent can infer it is called when a soft keyboard is covering the UI. There is no statement of when not to call it, what happens if no keyboard is present, or whether it should precede a tap on an obscured element.

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