Skip to main content
Glama
FerroxLabs

TVControl

by FerroxLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capture_screenshot

Capture the current TradingView chart view as a PNG to verify visuals. Supports full-page, active pane, or strategy tester capture, with wait-for-render and hidden-tab handling.

Instructions

Take a screenshot of the TradingView chart. REFUSES on a hidden tab, because a hidden tab returns the last frame it painted - a real PNG of the right chart showing stale data. region:"chart" captures the ACTIVE pane and reports which selector found it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoCapture method: cdp (Page.captureScreenshot) or api (chartWidgetCollection.takeScreenshot) (default cdp)
regionNoRegion to capture: full, chart, strategy_tester (default full). "chart" targets the focused pane.
filenameNoCustom filename (without extension)
allow_hiddenNoCapture even when the tab is hidden. The image may be a stale frame: only pass this if you have accepted that.
wait_for_renderNoWait for the chart canvas to stabilize before capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.5.3
    • addedInput schema / properties / allow_hidden
      Added value: +{
+  "description": "Capture even when the tab is hidden. The image may be a stale frame: only pass this if you have accepted that.",
+  "type": "boolean"
+}
    • changedInput schema / properties / region / description
      Previous value: -"Region to capture: full, chart, strategy_tester (default full)"New value: +"Region to capture: full, chart, strategy_tester (default full). \"chart\" targets the focused pane."
  2. First observedv2.2.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does well by revealing the hidden-tab refusal, explaining why the returned image could be stale, and noting that region:'chart' reports the selector used. It does not describe the output format, but the key safety and correctness caveats are transparent.

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 compact and front-loaded with the primary action. The hidden-tab warning and region clarification are high-value additions, and every sentence earns its place without redundant 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?

For a tool with five optional parameters and no output schema, the description covers the most critical behavioral caveats and parameter nuances. It could go further by explaining what the tool returns or how method choices (cdp vs api) affect results, but the combination of schema and description is largely sufficient for an agent to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying that region:'chart' captures the active pane and reports which selector found it, and by explaining the hidden-tab behavior relevant to allow_hidden. This exceeds what the parameter list alone communicates.

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 verb and resource: 'Take a screenshot of the TradingView chart.' It also adds meaningful scope details like region:'chart' capturing the active pane. It does not explicitly differentiate from sibling tools by name, but the core purpose is unambiguous.

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 provides important usage context: it refuses on hidden tabs and warns about stale frames, and it explains that region:'chart' targets the active pane. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it beyond the hidden-tab caveat.

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