Skip to main content
Glama
Sign In
mcp-gtv

mcp-gtv

by kud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gtv_type_text

Types provided text into the focused input field on a Google TV device using IME, enabling direct text entry without keycode mapping.

Instructions

Type arbitrary text into the focused field on the current device via IME (no keycode mapping).

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type into the focused field

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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. It discloses the IME method and lack of keycode mapping, but does not specify behavior when no field is focused, supported character sets, or potential side effects. It adds moderate behavioral context but lacks completeness.

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?

The description is a single, concise sentence that front-loads the essential information (action, target, method). Every word earns its place with no redundancy or filler.

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?

Given the tool's simplicity (one parameter, no output schema) and lack of annotations, the description adequately covers the tool's purpose and behavior. It does not mention error handling or fallbacks, but for a straightforward text input tool, it is sufficiently complete.

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?

The input schema has 100% coverage for the single 'text' parameter, already describing it as 'Text to type into the focused field'. The description adds no extra parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 action ('Type arbitrary text'), the target ('into the focused field'), and the method ('via IME'). It also distinguishes from sibling tool 'gtv_send_key' by noting 'no keycode mapping', making the purpose precise and unique.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (for direct text input) versus alternatives like gtv_send_key (for key presses). It does not explicitly state exclusions or name the sibling, but the context is clear enough for an agent to differentiate.

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