Skip to main content
Glama
Sign In
TradingView OpenCode Agent

TradingView OpenCode Agent

by jadatorin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capture_screenshot

Capture chart screenshots with optional filename and full-page support for AI-powered analysis in TradingView.

Instructions

Capture chart screenshot

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

Input Schema

NameRequiredDescriptionDefault
filenameNoOutput filename
full_pageNoCapture full page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It offers no information on file handling (e.g., overwrite behavior), output format, or side effects. This is insufficient for a tool that likely writes files.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (three words), but this brevity leaves out critical context. It is not well-structured for quick comprehension of what the tool does and its implications.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (parameter count 2, no output schema) and the lack of annotations, the description should explain what the screenshot captures, the output format, and any file naming behavior. It fails to provide sufficient context.

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 the parameter descriptions are present, so the baseline is 3. The tool description does not add any additional meaning beyond what the schema already provides.

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 tool captures a chart screenshot, which is a specific verb+resource action. While it does not explicitly differentiate from siblings, the sibling tools are sufficiently distinct in nature.

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?

No guidance is provided on when to use this tool versus alternatives. There are no prerequisites, context, or examples to help an agent decide when capturing a screenshot is appropriate.

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