Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pine_get_console

Read-only

Read only currently visible Pine console rows.

Instructions

Read only currently visible Pine console rows.

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

Input Schema

NameRequiredDescriptionDefault
target_idNoExact Chrome tab target ID from browser_list_tabs. Required for changes.
expected_layout_idNoExpected saved-layout ID. A mismatch stops the operation before writing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Read only' is redundant. The most useful addition is 'currently visible,' which signals that off-screen or historical console rows are excluded, but the description does not explain limits, ordering, or whether the console must be open.

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?

It is a single front-loaded sentence with no wasted words. The terseness is more a symptom of under-specification than poor conciseness, but the structure itself is clean.

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?

This is a simple read tool with annotations and a fully described schema, so the essentials are covered. However, with no output schema in place, the description could say more about what a 'row' contains or what the result looks like when the console is empty or not open.

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?

Schema coverage is 100% and both parameters are optional, so the schema already explains target_id and expected_layout_id. The description adds no parameter-level meaning beyond that baseline, which is acceptable given complete schema coverage.

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 has a clear verb and resource ('Read ... Pine console rows') and adds a scope qualifier ('currently visible'). It does not name or distinguish itself from similar siblings such as pine_get_errors or data_get_pine_lines, so it falls short of a 5.

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?

There is no explicit guidance on when to use this tool versus pine_get_errors, data_get_pine_lines, or other Pine inspection tools. The phrase 'currently visible' implies the console must be open, but the reader is left to infer that prerequisite.

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