Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ui_type_text

Types text into the focused input or textarea element, enabling automated entry into TradingView chart inputs and forms.

Instructions

Type text into the currently focused input/textarea element

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type into the focused element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits itself. It does state the key precondition that the target must be the currently focused element, but it fails to mention whether existing text is replaced or appended, how special characters are handled, or what happens when no editable element is focused.

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, compact sentence that front-loads the action and target. It contains no filler or redundant information, making it highly efficient.

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 tool with one parameter and no output schema, the description is mostly adequate and the focused-element precondition is useful. However, the ambiguity around whether typing overwrites or appends existing content, and the lack of error behavior when no focus exists, leave meaningful gaps for an agent.

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 single `text` parameter is fully documented in the input schema (100% coverage), so the description does not need to add much. The schema description 'Text to type into the focused element' already covers the parameter's meaning, leaving no additional semantic gap.

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 explicitly uses the verb 'Type' and specifies the resource as 'the currently focused input/textarea element', making the tool's function immediately clear. It is distinguishable from sibling UI tools like ui_click and ui_keyboard because it focuses on text entry into editable fields.

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 description implies the intended use case: typing text into an already-focused editable element. However, it provides no explicit guidance on when to use this tool versus alternatives like ui_keyboard, nor does it state prerequisites beyond the 'currently focused' condition.

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